Allow string_list flags to be set via repeated flag uses #15943
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.
For all parts of Bazel other than option parsing, string build setting
flags with
allow_multiple = True
should behave just likestring_list
settings, even though they are fundamentally of a different type. This
requires a lot of special casing all over the code base and also causes
confusing user-facing behavior when transitioning on such settings.
This commit deprecates the
allow_multiple
named parameter ofconfig.string
and as a replacement introduces a new named parameterrepeatable
onconfig.string_list
. Settings with the latter set to Truebehave exactly like
string
settings withallow_multiple = True
withrespect to command-line option parsing and exactly like ordinary
string_list
flags in all other situations.Fixes #13817
Closes #14911.
PiperOrigin-RevId: 462146752
Change-Id: I91ddc4328a1b2244f4303fcda7b4228b182a5d56