-
Notifications
You must be signed in to change notification settings - Fork 386
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
chore: move common dependencies to workspace Cargo.toml #1388
Conversation
Thanks for the PR! Every crate of Yazi gets published to crates.io, will this have any impact on it? |
I don't believe it should cause any issues. quickwit makes use of workspace dependencies, and their crates get published as well. |
Nice, TIL about that. |
color_quant = "1.1.0" | ||
crossterm = "0.27.0" | ||
futures = "0.3.30" | ||
crossterm = { workspace = true } |
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 can't use { workspace = true }
here because the "use-dev-tty" feature can only be enabled on macOS systems.
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.
Ah, I see. I hadn't realized. I pushed a fix. { workspace = true, features = [ "use-dev-tty" ] }
lets the version be defined once in the root Cargo.toml, but with additive features. Details here: https://doc.rust-lang.org/cargo/reference/workspaces.html#the-dependencies-table
33d04f9
to
3fdbbfe
Compare
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.
LGTM, thanks!
It's easier to keep versions in sync across the entire workspace this way.