-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add ui.searchFields
option
#6165
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/Fa2ogVKQjt4DuzE8onEVFSeM9UVu |
🦋 Changeset detectedLatest commit: e197d51 The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
enum QueryMode { | ||
default | ||
insensitive | ||
} |
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.
Note the naming and enum values here align with the mode
field that will be in the new filters for strings (and since the new filters align with Prisma, so does this).
Co-authored-by: Tim Leslie <[email protected]>
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.
👍
This is primarily to remove the usage of the
search
argument in the Admin UI because we're planning on removing it soon because people may think that it's proper full-text search which it is not and we recommend people usecontains
filters directly(which is what thesearch
argument does) until Prisma supports full-text search and we expose it in the GraphQL API.