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.
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
[Controls] Allow wildcard searching in options list #158427
[Controls] Allow wildcard searching in options list #158427
Changes from 30 commits
0678560
94c718c
a09faaa
8bd7650
d3eb86e
837eabc
434fe84
4eb520b
e402117
2468414
f7b6226
e4671ec
0f36492
57b44f6
bac225c
312f5b4
f3b0d0a
8291f6f
ccaad0e
cc96abf
4326c1c
95624b1
c38465f
db67256
b7d4f23
45860ab
b51ee83
fb8cd7a
a415401
c692463
e282238
8ae0b3b
79297e7
4f76348
f4d92a9
6e3247f
cf5b2e0
1a6cde8
7f0aeab
6601b7f
1da2197
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Originally, I had this as a boolean
wildcardQuery
property that would be true only if the user selected the "contains" search technique; however, after further thought about extensibility and preventing migrations, I think it makes more sense to store this as a string value.After all, right now we only support two search types (both of which only work for "string" type fields) - "prefix" and "contains" searching. But what about when we add support for number fields to the options list control - perhaps search techniques like "less than" and "equal to" might make more sense? Or right now, we have essentially a version of "contains" for IP fields - but maybe this doesn't always make sense, and we want to introduce other searching techniques for IP fields in the future? Having the search technique stored as a string from the very beginning rather than a boolean value allows for these changes without having to worry about a potential migration :)