Is your feature request related to a problem? Please describe
The module currently returns result objects from the search provider and then puts this data into a Field object before returning this to a template.
users often want to do some customisation of this object and in some cases expect it to be a Silverstripe DataObject. This leads to a bit of confusion where its not clear where to store data or how to output it on the template. Eg people might ask 'should I create an indexed field that contains what I want to display on results' or ' can I use LimitCharacters on the results'.
Describe the solution you'd like
It would be great if there was a way to allow more customisation of results. Ideally this is without making this module tightly coupled to the forager modules. It could be an extension point or some other API for processing the results before handing them to the template.
Describe alternatives you've considered
- ResultsProcessor from the elastic module is already injectable so that could be a way to change the behaviour - could be some documentation around how to do this. Or maybe the process results method could become part of the SearchAdapter interface to move it 'up' into the forager module a bit.
Is your feature request related to a problem? Please describe
The module currently returns result objects from the search provider and then puts this data into a Field object before returning this to a template.
users often want to do some customisation of this object and in some cases expect it to be a Silverstripe DataObject. This leads to a bit of confusion where its not clear where to store data or how to output it on the template. Eg people might ask 'should I create an indexed field that contains what I want to display on results' or ' can I use LimitCharacters on the results'.
Describe the solution you'd like
It would be great if there was a way to allow more customisation of results. Ideally this is without making this module tightly coupled to the forager modules. It could be an extension point or some other API for processing the results before handing them to the template.
Describe alternatives you've considered