Investigate whether implementation can be improved using observers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Bevy 0.14 introduces the concept of Observers, which will be a building block for relations. Observers have a lot in common with the reactive nature of workflows and services, although they are not a direct replacement. Still, they may be able to yield performance improvements (less need for exclusive systems?) or at least a cleaner implementation of workflows and services.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing the current workflows and services implementation alongside Bevy 0.14 observers, then determine whether observers provide measurable performance improvements or a cleaner implementation. Done means documenting a clear conclusion and the supporting evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100