Suggestion: Add `matchingTerms` array to `search()` output about orama

[micheleriva]

Hi @Yorkshireman , thanks for your feature request. Do you happen to have a reference of other search engines implementing this feature? I'd like to see how they manage it

[Yorkshireman]

Hi @Yorkshireman , thanks for your feature request. Do you happen to have a reference of other search engines implementing this feature? I'd like to see how they manage it

Hi Michel, I don't sorry. I know I've been a bit lazy so far - I haven't looked at the source code of lyra properly yet, but I would think it wouldn't be too difficult to "pluck out" the term that "caused" the hit and push it into a matchingTerms array? I am talking from a completely ignorant position here though of course so I could be very wrong!

[Yorkshireman]

Ah you're probably wondering what is best to do rather than how. Yes makes sense.

[micheleriva]

Closing this as #150 fixes the search algorithm. Multiple terms queries are OR by default now

[simonwiles]

I'm looking at replacing a lunr.js -based system, and I've just been taking lyra for a spin -- it performs very nicely! But this is necessary functionality for this particular case (either returning the terms matched as they appear in the the original context or a [start, end] offset -- lunr.js offers both). Or perhaps an extracted snippet could also work. Is there any likelihood of this being on your roadmap in the future? Thanks!