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
feat: merge user-provided --{disable,enable}-features in args #11152
Conversation
c28874f
to
d35eab7
Compare
Is it the case? I would expect that user-provided args override the default ones. |
d35eab7
to
7158edf
Compare
Yes. If you want to test it out locally, run this script:
Then observe that a log message will appear in the page that says |
7158edf
to
03e01eb
Compare
017c389
to
ff53762
Compare
ff53762
to
2ce2f59
Compare
.map(s => { | ||
return s.split(new RegExp(`${flag}` + '=\\s*'))[1]?.trim(); | ||
}); | ||
return opts.length === 0 ? [] : opts.join(',').split(','); |
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.
return opts.length === 0 ? [] : opts.join(',').split(','); |
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.
The first suggestion was actually wrong. opts
was created as an intermediate value. I was having compilation issues otherwise
9cd5068
to
2ce2f59
Compare
Done |
99f6c62
to
322e462
Compare
322e462
to
13fc424
Compare
Currently user-provided features are completely ignored in args, being overridden with default ones.
13fc424
to
bcf29f2
Compare
Currently user-provided features are completely ignored in args, being overridden with default ones.
Bug: #11072