-
-
Notifications
You must be signed in to change notification settings - Fork 809
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
[3.6] Allow fields to be unsearchable #7381
base: 3.6
Are you sure you want to change the base?
Conversation
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.
Implemented both for Storage as well as legacy! 👍
Oi, it's the Storage of the Legacy. I think (only) @rossriley knows how it really works with the new one. |
As discussed in #development as this is a feature, we're pushing to |
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.
Migrate to new layer
This issue has been automatically marked as stale because it has not had recent activity. Maybe this issue has been fixed in a recent release, or perhaps it is not affecting a lot of people? |
I personally think setting |
actually haven't tried that, does it work? |
Setting it to |
This is a new feature in the legacy part of Bolt. The fix was simpler than I thought.
Use Case
For some clients, we add a
textarea
-type field for notes; however, the search still searches this and highlights the keywords in that field. My initial thought was to set thesearchweight
to something low, but a lowsearchweight
does not mean it's filtered.Usage
Add
searchable: false
to your field definition:field_notes: &field_notes notes: label: Notes type: html height: 300px + searchable: false
Update with related Docs PR: bolt/docs#888