fix bugs with workspace
key and update_toml
#10685
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivations and Context
When working on an external subcommand to help with the switch to workspace inheritance, I found issues with the output
Cargo.toml
it was creating. When acargo_add::Dependency
would change its source to aWorkspsaceSource
,workspace = true
would not show up. This lead me to discover that thedefault-features
key was not being removed when theworkspace
key was set.This fixes those issues but brought up questions about how to deal with removing keys and clearing conflicting fields in a
Dependency
. After talking with @epage, it was decided that this was the minimal set of changes to make while the changes to fix the other issues is workshopped.Changes
default-features
to the list of keys to remove when the source is aWorkspaceSource
workspace
key when the source is aWorkspaceSource