-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
How to set default 'add filter' match type #3001
Comments
We noticed a similar issue. From my internal team: It used to be, when you added a search parameter in rails admin, it would default the parameter type to "contains." Starting on the 26th of February (best I can tell), it left the parameter type blank, forcing the user to select one prior to searching: This is a minor change but it is an extra step for an action that we do upwards of 50 times a day. Can this be changed back so that it defaults to "contains"? |
Our team would also like to be able to specify a default match type, and not always "contains". So having the default configurable would be great. We may be able to look into adding this behavior, but no promises. |
I solved it by defining the following in a
I basically override the original method and set the operator to |
I was able to solve this by adding
to the |
Following #3318 (released in |
I have searched and read a lot but I can't find any hints on how to do this.
When I 'add filter' per the picture below the default match is ... which does nothing. See picture below.
I want to set the default matching to contains. I want contains to be showing and be used with no user interaction. If they want to change it from that they can. It will be the default though rather than ...
Can someone point to docs or tell me how to do that?
The text was updated successfully, but these errors were encountered: