docs: adjust mvp effects for bevy 0.16 design considerations #15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some modern features of bevy need to be accounted for in the effects mvp. Some of these may be older than bevy 0.16, but I was not familiar with all of them as the last bevy version I had intense contact with was 0.12-ish.
In particular, running systems with commands, observers, relations, and error handling are all pretty new. These are now accounted for in the mvp checklist, with some things merely being "nice to have".
Eitherhas been tossed in here as well, which should have probably been included in the first place.