-
Notifications
You must be signed in to change notification settings - Fork 1.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
Update all examples, all tests, and egui_demo_app
to use env_logger 0.11
#4949
base: master
Are you sure you want to change the base?
Conversation
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.
I additionally ran scripts/check.sh
- seems to work!
@bircni Thanks! I'm on windows so I couldn't run that shell script - which is why I pointed to the Github Action run, because I was pretty sure it'd run |
The script is for Linux only 😊 |
version = "0.2.2" | ||
source = "registry+https://github.com/rust-lang/crates.io-index" | ||
checksum = "06abde3611657adf66d383f00b093d7faecc7fa57071cce2578660c9f1010821" | ||
|
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 adds a lot of dependencies - is there a way to avoid them with feature-flags on env_logger
, or by using an alternative crate?
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.
I don't think so.
That said, these extra dependencies are only compiled alongside examples and tests - not alongside egui
itself. Thus, I doubt they'll be much of an issue, unless you're constantly running cargo clean
.
Is there anything blocking this from being merged? |
This PR updates all examples, all tests, and the
egui_demo_app
crate to use the latest version of env_logger,0.11
. This helps to clean up the list of outdated crates listed when runningcargo outdated --root-deps-only --workspace
.To ensure I didn't break anything, I ran
cargo build --all-features --all-targets
(and the same withcargo test
), and saw nothing that made me feel that I broke anything. Additionally, the CI run for my commit finished successfully: https://github.com/LikeLakers2/egui/actions/runs/10347887485Before making this PR, I did take notice of a similar PR, #4164, but because it's a 5-month-old draft that appears to be abandoned, I decided to make this PR.