-
Notifications
You must be signed in to change notification settings - Fork 881
chore: implement wildcard style matching for build param values #12695
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
chore: implement wildcard style matching for build param values #12695
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
8112eb2
to
aecf9c0
Compare
ad20f9c
to
d4fb951
Compare
aca699c
to
2bcdbd9
Compare
d4fb951
to
9618597
Compare
2bcdbd9
to
819e861
Compare
I am going to close this because it makes our search terms more inconsistent. We can reopen this if we decide we need it in the future. It mainly is helpful for list style params. |
Allows using
*
to match wildcard type regex. This is useful because we allow list types in our param values. Without this if you had a list option, it would be tricky to match all params that contain some element in the list.Demo:
Screencast.from.2024-03-20.15-10-49.webm
The Problem
Only this 'param' term supports this right now. Others do not, so it's not consistent across all other search terms.