[3.6] Allow fields to be unsearchable

[xiaohutai]

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 the searchweight to something low, but a low searchweight 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

[bobdenotter]

Implemented both for Storage as well as legacy! 👍

[xiaohutai]

Oi, it's the Storage of the Legacy. I think (only) @rossriley knows how it really works with the new one.

[GwendolenLynch]

As discussed in #development as this is a feature, we're pushing to unstable … plus we've pushed back on legacy changes for a long while now, so we'll all collaborate on getting this into 3.6 as an update to the new layer.

[GwendolenLynch]

Migrate to new layer

Moving to "new"

[stale]

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?
It will be closed if no further activity occurs, because we like to keep the issue queue concise and actual.
If you think this issue is still relevant, please let us know. Especially if you’d like to help resolve the issue, either by helping us pinpointing the cause of a bug, or in implementing a fix or new feature.

[JarJak]

I personally think setting searchweight: 0 should do the same trick.

[rossriley]

actually haven't tried that, does it work?

[bobdenotter]

Setting it to searchweight: 0 means that found terms in the field don't affect the search results. However, these fields will show up in the list of results.