Add option to pieces and pages to specify search summary
See original GitHub issueThe searchSummary
property on items in the search page index can be very unreadable. There is an option to set silent: true
on fields to exclude them (as I understand this), but in many cases it would be easier to specify a single field to be used for the search summary.
Describe the solution you’d like
Add the ability to set searchSummary: true
on a field schema to use that field as the search summary for the respective piece or page type. If an area gets this property set, the plain text version of that area would be used. Only one field could be set this way, since unintended field order could defeat the intended purpose.
Describe alternatives you’ve considered
It seems that setting silent: true
on all the other fields is the current alternative.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (7 by maintainers)
Top GitHub Comments
I think this could make
searchSummary
more of a first-class citizen. My thought is that one could make the search index very complex, with conditionals for the different document types to show various fields (I’ve done this and it gets ugly fast), or keep that simple with this property set in the schema.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.