-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better Debug support for Bevy ECS #1130
Comments
This is improved by #1525, with a Debug impl for World. |
@alice-i-cecile What remains to be coded to complete this issue for now? |
I would like debug impls for:
Once that's done I think we can close this out in favor of more specific issues. |
I'll take a look to see if I can do any of those. |
WRT |
…ate, etc. (#6214) # Objective - Adding Debug implementations for App, Stage, Schedule, Query, QueryState. - Fixes #1130. ## Solution - Implemented std::fmt::Debug for a number of structures. --- ## Changelog Also added Debug implementations for ParallelSystemExecutor, SingleThreadedExecutor, various RunCriteria structures, SystemContainer, and SystemDescriptor. Opinions are sure to differ as to what information to provide in a Debug implementation. Best guess was taken for this initial version for these structures. Co-authored-by: targrub <62773321+targrub@users.noreply.github.com>
…ate, etc. (bevyengine#6214) # Objective - Adding Debug implementations for App, Stage, Schedule, Query, QueryState. - Fixes bevyengine#1130. ## Solution - Implemented std::fmt::Debug for a number of structures. --- ## Changelog Also added Debug implementations for ParallelSystemExecutor, SingleThreadedExecutor, various RunCriteria structures, SystemContainer, and SystemDescriptor. Opinions are sure to differ as to what information to provide in a Debug implementation. Best guess was taken for this initial version for these structures. Co-authored-by: targrub <62773321+targrub@users.noreply.github.com>
…ate, etc. (bevyengine#6214) # Objective - Adding Debug implementations for App, Stage, Schedule, Query, QueryState. - Fixes bevyengine#1130. ## Solution - Implemented std::fmt::Debug for a number of structures. --- ## Changelog Also added Debug implementations for ParallelSystemExecutor, SingleThreadedExecutor, various RunCriteria structures, SystemContainer, and SystemDescriptor. Opinions are sure to differ as to what information to provide in a Debug implementation. Best guess was taken for this initial version for these structures. Co-authored-by: targrub <62773321+targrub@users.noreply.github.com>
…ate, etc. (bevyengine#6214) # Objective - Adding Debug implementations for App, Stage, Schedule, Query, QueryState. - Fixes bevyengine#1130. ## Solution - Implemented std::fmt::Debug for a number of structures. --- ## Changelog Also added Debug implementations for ParallelSystemExecutor, SingleThreadedExecutor, various RunCriteria structures, SystemContainer, and SystemDescriptor. Opinions are sure to differ as to what information to provide in a Debug implementation. Best guess was taken for this initial version for these structures. Co-authored-by: targrub <62773321+targrub@users.noreply.github.com>
…ate, etc. (bevyengine#6214) # Objective - Adding Debug implementations for App, Stage, Schedule, Query, QueryState. - Fixes bevyengine#1130. ## Solution - Implemented std::fmt::Debug for a number of structures. --- ## Changelog Also added Debug implementations for ParallelSystemExecutor, SingleThreadedExecutor, various RunCriteria structures, SystemContainer, and SystemDescriptor. Opinions are sure to differ as to what information to provide in a Debug implementation. Best guess was taken for this initial version for these structures. Co-authored-by: targrub <62773321+targrub@users.noreply.github.com>
What problem does this solve or what need does it fill?
Debugging and troubleshooting ECS problems in
Describe the solution would you like?
Derive Debug for query filters, World, App, AppBuilder etc.
Describe the alternative(s) you've considered?
Write custom wrappers every time to extract and then display the information that I care about each time that I'm debugging these parts of the core logic.
Additional context
Creating a sensible debug output for some of the larger objects (like App and World) seems challenging; a pattern for doing so in a more / less verbose fashion would be welcome.
The text was updated successfully, but these errors were encountered: