Enhancement: Default filter operator for fields#3318
Merged
mshibuya merged 7 commits intoFeb 28, 2021
Conversation
Member
|
Looks good, thanks! |
This was referenced Mar 15, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue
When a filter is initially added on the filter criteria on a list view, the default operator is
nilor empty which makes it necessary for the user to select an operator each time they add a filter. This can be a bit cumbersome especially if users search a field by a particular operator the majority of the time.Proposed change
A field option to set a default filter operator for a field which populates the filter operator select box when initially added to the filter criteria. If one is not specified then it will default to the original behavior of setting the operator to
nilor empty.