You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we only highlight results of dataFields which are being rendered in the view ignoring their sub-fields. For certain search use-cases where there won't be a full-word match, we only receive such highlights in the sub-fields (.search field w.r.t. appbaseio standard mappings). For example:
For results, where we don't have anything highlighted, we are receiving the marked highlights in .search subfield. So, it's best to unionise the highlight-results of dataFields with their respective sub-fields before rendering.
Reactivesearch version: 2.6.2
The text was updated successfully, but these errors were encountered:
One option here is to transparently pass the highlight key returned from the response in the onAllData and onData callbacks (will be renderAllData and renderData in v3.0.0).
Issue
Enhancement
Description
Currently, we only highlight results of
dataFields
which are being rendered in the view ignoring their sub-fields. For certain search use-cases where there won't be a full-word match, we only receive such highlights in the sub-fields (.search
field w.r.t. appbaseio standard mappings). For example:For results, where we don't have anything highlighted, we are receiving the marked highlights in
.search
subfield. So, it's best to unionise the highlight-results ofdataFields
with their respective sub-fields before rendering.Reactivesearch version: 2.6.2
The text was updated successfully, but these errors were encountered: