- Issue created by @tuwebo
- 🇪🇸Spain tuwebo
Just adding a patch, to check it with that code will be enough.
- 🇩🇪Germany mkalkbrenner 🇩🇪
I don't know the consequences in combination with Search API.
Could you add some tests?
Currently, the SearchApiSolrBackend and Utility classes use $parse_mode_id for some logic. I propose that we retrieve this value from `getBaseId()` instead of `getPluginId()`.
If I want to change the query keys like:
"foo bar"
to
"foo"
It would be beneficial to add a parse_mode plugin to handle this transformation. However, I am uncertain whether the correct approach is to override the getPluginId() function in the custom plugin. Alternatively, it might be more effective for SearchApiSolrBackend and Utility classes to rely on getBaseId() for obtaining the $parse_mode_id, allowing me to name my plugin like:
id = 'terms:my_custom_plugin_id'
I am not sure about the implications or if I am completely wrong with this approach, but at first sight it looks like there is no side effects neither in Search Api nor Search Api Solr.
Active
4.0
Code
Just adding a patch, to check it with that code will be enough.
I don't know the consequences in combination with Search API.
Could you add some tests?