-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Ambiguity checker emits a lot of warnings with default plugins #1868
Comments
Hmm, this issue seems like the correct place to continue the discussion that started in #1606 :) |
This actually is part of the reason I've created stages that come after |
An easy solution would be to allow filtering the ambiguities, something like app.insert_resource(ReportExecutionOrderAmbiguities::filter(|name| name.contains(env!("CARGO_PKG_NAME"))) would only display the ambiguities in the current crate. In the future (probably when there is an editor) there could be an |
Whoops, misclick 😅 |
The intended solution is to add all default systems into their own, private ambiguity set. This will need to be hardcoded; two options:
|
Will be resolved-ish by #2766. |
This has been fixed. |
Bevy version
0.5
Operating system & version
Windows 10
What you did
What you expected to happen
No ambiguities reported.
What actually happened
My terminal was flooded with ambiguity warnings:
The text was updated successfully, but these errors were encountered: