Convert `HierarchyQueryExt` to use a `SystemParam` instead of an extension trait
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 171
Description
> I wonder if it would be a good idea to convert HierarchyQueryExt into system params instead 🤔 what is the reason it is an extension in the first place?
I'm pretty sure it predates the `SystemParam` derive macro, and has grown organically from there. I really like the filtering capabilities, but I agree: I think that the SystemParam approach is a lot simpler as both a user and a maintainer. Adding a filter generic should be totally doable. Follow-up though!
_Originally posted by @alice-i-cecile in https://github.com/bevyengine/bevy/issues/15627#issuecomment-2395218671_
Contributor guide
Research direction
Start by locating the existing HierarchyQueryExt entry point and reviewing how SystemParam is used in the project. The issue names no files or tests; done means converting the extension trait to a SystemParam while preserving its filtering capabilities and confirming the resulting API works for users and maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- game-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100