-
Notifications
You must be signed in to change notification settings - Fork 386
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
Make config vectors optional. #801
Conversation
67b20fd
to
fc0a731
Compare
If we use optional variables for config options, then this is required for us to be able to differentiate if a variable is provided and empty, or simply not provided. For example, if we have: [build.env]
passthrough = [] We currently cannot differentiate it from: [build.env] When merging, this means we do not know if we need to overwrite the value, or not. What this does is it changes all |
fc0a731
to
462e40a
Compare
Both resolved, I made it so there's an |
Allows us to differentiate between an empty array and an array that was not provided when merging config files. cross-rs#754 (comment) Required for cross-rs#754.
462e40a
to
830f836
Compare
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.
bors r+
Build succeeded: |
Allows us to differentiate between an empty array and an array that was not provided when merging config files.
#754 (comment)
Required for #754.