Comprehensive Source Tracking
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 161
Description
Bevy code can get very spread out. It's not uncommon for very well separated pieces of machinery to have to coordinate, often across crate boundaries. Bevy has great tools to accomplish this sort of coordination, but it is often hard to inspect.
The first attempt at improving runtime inspection was made in https://github.com/bevyengine/bevy/pull/14034, which added optional tracking of exactly where every component is accessed or mutated, as an extension of the change detection system. But there's still several other places we don't track this information.
+ [x] #16776
+ [ ] #15607
+ [ ] #16047
+ [ ] Add source location tracking to resource access.
+ [x] #16852
+ [ ] Expose source tracking through the remote protocol.
Contributor guide
Assessment
This issue has not been assessed yet.