-
Notifications
You must be signed in to change notification settings - Fork 2
Effectful system map debug #162
Copy link
Copy link
Open
Labels
A-System-CombinatorsArea - concerning system combinators.Area - concerning system combinators.C-FeatureCategory - making something new possible.Category - making something new possible.D-ModestDifficulty - new features, refactors, and challenging bug fixes.Difficulty - new features, refactors, and challenging bug fixes.S-Ready-For-ImplementationStatus: this issue is ready for someone to pick it up and open a PR!Status: this issue is ready for someone to pick it up and open a PR!
Description
Activity
Metadata
Metadata
Assignees
Labels
A-System-CombinatorsArea - concerning system combinators.Area - concerning system combinators.C-FeatureCategory - making something new possible.Category - making something new possible.D-ModestDifficulty - new features, refactors, and challenging bug fixes.Difficulty - new features, refactors, and challenging bug fixes.S-Ready-For-ImplementationStatus: this issue is ready for someone to pick it up and open a PR!Status: this issue is ready for someone to pick it up and open a PR!
One benefit of
bevy_pipe_affectis being able to process effects before they are performed. One thing I've done a couple times is look at the effect my system is having by debugging it in an intermediate system... Something like.my_effectful_system .map(|ef| { dbg!("{ef:?}"); ef }) .pipe(affect)It'd be nice if this library provided a simple mappable debug function like that, so it only takes 1 line instead of 4.