-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Error when --group includes non-existent groups #8394
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
Conversation
386c7e6 to
26e9cf2
Compare
crates/uv-resolver/src/lock/mod.rs
Outdated
|
|
||
| // Validate any requested dependency groups. | ||
| for group in dev.groups().iter() { | ||
| if !root.metadata.requires_dev.contains_key(group) { |
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 love using metadata here (rather than root.dev_dependencies) because this metadata is mostly just intended for lockfile validation / caching (we invalidate the lockfile when the metadata changes). But if we use root.dev_dependencies, we will also fail if the user does --group foo when foo is empty. It seems wrong to fail when requesting a valid but empty group, so...
26e9cf2 to
9d813ad
Compare
bb83978 to
c246fbf
Compare
64045ed to
07b5f8c
Compare
07b5f8c to
417ecad
Compare
## Summary Part of #8272.
## Summary Part of #8272.
## Summary Part of #8272.
## Summary Part of #8272.
## Summary Part of #8272.
Summary
Part of #8272.