Score exact matches higher over location about fuse HOT 4 CLOSED

I've attached a test case that runs with Node.js and has some example data attached to it. Running queries for it for the terms "egg" should illustrate what I mean.

Granted if you do search "eggs" it puts more relevant results to the top, but it still gives a lower score towards items with "egg" because of location over partial matches.
Hope this helps, thanks.

The data might be a bit weird, but it's from actual production data I'm working with which I have extracted here for demonstration purposes.

FuseExample_78.zip

from fuse.

Thanks for test cases, I will take a look!

from fuse.

Not sure if this is more related to #77 , but if for example you change data to:

[
  {
    "name": "Eggs"
  }
]

For query: "egg"
Fuse 2.0.X will not return the Eggs item, 1.3.1 will however.

Sorry for not being much help other than raising issues, I'm still working on understanding the algorithm.

from fuse.

I was experiencing the same issue and reverted back to 1.3.1

from fuse.