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
Remove redundant imports #12817
Remove redundant imports #12817
Conversation
Found using `cargo check --workspace --tests`.
Found using `cargo check --workspace --examples`.
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.
We should probably extend CI to do these checks with these extra flags.
# Objective - The `ImePreedit` component from [`text_input`](https://github.com/bevyengine/bevy/blob/50699ecf76800e5b1b31bd9b6845b30e4ede5e32/examples/input/text_input.rs#L126-L127) appears to be unused. - This was found by running `cargo check --workspace --examples`, originally as part of #12817. ## Solution - Remove it :)
Removed the label because it's a draft |
Yup, I just need to update the CI and I'll mark it as ready. |
I added a check into CI, but it's not amazing. I think the tool needs a refactoring, but for now this PR is ready to go. |
Co-authored-by: François Mockers <francois.mockers@vleue.com>
…ngine#12818) # Objective - The `ImePreedit` component from [`text_input`](https://github.com/bevyengine/bevy/blob/50699ecf76800e5b1b31bd9b6845b30e4ede5e32/examples/input/text_input.rs#L126-L127) appears to be unused. - This was found by running `cargo check --workspace --examples`, originally as part of bevyengine#12817. ## Solution - Remove it :)
# Objective - There are several redundant imports in the tests and examples that are not caught by CI because additional flags need to be passed. ## Solution - Run `cargo check --workspace --tests` and `cargo check --workspace --examples`, then fix all warnings. - Add `test-check` to CI, which will be run in the check-compiles job. This should catch future warnings for tests. Examples are already checked, but I'm not yet sure why they weren't caught. ## Discussion - Should the `--tests` and `--examples` flags be added to CI, so this is caught in the future? - If so, bevyengine#12818 will need to be merged first. It was also a warning raised by checking the examples, but I chose to split off into a separate PR. --------- Co-authored-by: François Mockers <francois.mockers@vleue.com>
Objective
Solution
cargo check --workspace --tests
andcargo check --workspace --examples
, then fix all warnings.test-check
to CI, which will be run in the check-compiles job. This should catch future warnings for tests. Examples are already checked, but I'm not yet sure why they weren't caught.Discussion
--tests
and--examples
flags be added to CI, so this is caught in the future?ImePreedit
component fromtext_input
example #12818 will need to be merged first. It was also a warning raised by checking the examples, but I chose to split off into a separate PR.