feat(cargo-metadata): add workspace_default_members#11978
feat(cargo-metadata): add workspace_default_members#11978bors merged 5 commits intorust-lang:masterfrom
workspace_default_members#11978Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
|
Pardon my changing it to draft. @rustbot author |
|
The team just agreed on adding this field 🎉. r? @weihanglo |
workspace_default_members
c3345df to
8d579e4
Compare
|
The rebase seems to be done incorrectly. Could you start over and fix that? |
|
☔ The latest upstream changes (presumably #11840) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Guess somewhat this pull request was messed up. You could either use Here are some references I found helpful:
Instructions to reviving this pull request are roughly like the followings: git switch master
git pull origin master
git switch metadata_workspace_default_members
git switch --create backup
git switch -
git reset --hard master
git cherry-pick 8d579e4cd54b9e4437a6c7c13040090589e5bb73 48dcdfa5f11cfcd2b5e3f8de709fb3fc5afb93ac 5ff0fbd8588d2bd633010e24d9b4eb48fd9e16b4 4461032952bda70cab10cdfb8926e34a60bd955d
# Then create a new PR or force push to this PR, or continue working on it locally. |
|
Thanks! @bors r+ |
|
☀️ Test successful - checks-actions |
What does this PR try to resolve?
Fixes #8033.
How should we test and review this PR?
I fixed one test "cargo_metadata_simple". Other tests haven't been updated, and potentially additional tests could be added to test the new functionality specifically.
Additional information
More tests would have to be updated. This change adds "workspace_default_members" to the ExportInfo struct which is serialized to json. I would imagine this could break existing testing infrastructure, but existing crates / apps reading this output should presumably expect that additional fields / data could be added.