Closed brandon-bethke-timu closed 6 years ago
Thanks for reporting, I was able to reproduce this issue. It looks like it is triggered when the search contains two required terms each scoped by a field but one that matches nothing.
I've tracked the bug down to the way that lunr.Set.complete
and lunr.Set.empty
are handled in lunr.Set#union
and lunr.Set#intersect
. I'll put together a bug fix and a new release in the next few days.
Hi, We have faced with the same problem so kindly request you to this fix this bug as soon as possible. We will be waiting a new release impatiently. Many thanks...
I have just published 2.3.1 which contains a fix for this issue.
The following code will throw an exception: TypeError: Cannot convert undefined or null to object