-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
SystemNodeId, SystemSetNodeId #10765
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
Conversation
It looks like your PR is a breaking change, but you didn't provide a migration guide. Could you add some context on what users should update when this change get released in a new version of Bevy? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a nice direction: more clearly distinguishing between these uses is valuable! My initial reaction was that it wouldn't be, since it's already wrapped in an enum, but since we're passing these values around directly, I much prefer the more strictly typed approach.
I'd like to have a little bit more documentation, especially on how these are generated and uniqueness is managed, but I'm overall very pleased with the diff.
|
Add
SystemNodeId
andSystemSetNodeId
types to be used whenNodeId
is known to be either of them.This should make code easier to read and slightly safer.