Open tgeoghegan opened 7 months ago
I don't want cargo-autoinherit
to become a formatter for Cargo.toml
manifests.
There's an ongoing initiative in the cargo
team to cover that need and it's better to avoid overlaps. At the same time,
what has been established so far doesn't cover workspace dependencies.
Given the above, I think we can consider adding a CLI option to cargo-autoinherit
to choose which style should be used for newly inherited dependencies.
That option will be deprecated once cargo
decides which style is "canonical".
autoinherit
will insert dependencies of the formfoo = { workspace = true}
. However a project might already have inherited dependencies written in the formfoo.workspace = true
. Either form is fine, what I really care about is consistency. So it'd be nice to either be able to choose a style when invokingcargo autoinherit
, or to have an option to rewrite inherited dependencies intoautoinherit
's preferred form.