-
Notifications
You must be signed in to change notification settings - Fork 243
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
Add Cargo Registry support to buf.plugin.yaml
#2956
Conversation
The plan is to land this on `main` (for the plugins repo) and then merge it over to `dev`.
// version_requirement specifies the version requirement of the dependency. | ||
string version_requirement = 2; | ||
// default_features specifies whether or not default features will be enabled for the dependency. | ||
bool default_features = 3; |
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.
Can you remind me, what happens if this is true
and we also specify features, it's additive? Or can you only set custom features if default is false.
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.
Had to check on this myself — best reference is https://doc.rust-lang.org/cargo/reference/features.html#the-default-feature. My understanding is that it's additive — default-features = true, features = ['xyz']
results in both the 'xyz'
and any features in the default
feature to be enabled.
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.
Got it, really doesn't matter for our purposes since it'll be a property of the plugin itself.
The plan is to land this on
main
(for the plugins repo) and then merge it over todev
. Draft until I PR over on plugins.