The score is always 1 when using extendedSearch and "include" match type #522

baibonjwa · 2020-12-14T06:36:55Z

Describe the bug

The score is always 1 and I cannot sort the results. Is this a bug or expected behavior?

Version

6.4.3

Minimal Reproduction

Demo: https://jsfiddle.net/baibonjwa/dcoL1nth/17/

skearney6 · 2020-12-23T00:55:46Z

Yes! This one was messing me up big time. I see that the scoring for this looks flipped in the code. I'm going to send a PR for that - hopefully it will be accepted quickly. 🤞

change score to 0/1 when matched/not matched, respectively fixes krisk#522

change score to 0/1 when matched/not matched, respectively fixes #522

baibonjwa added the bug label Dec 14, 2020

skearney6 added a commit to skearney6/Fuse that referenced this issue Dec 23, 2020

fix(extended): correctly score include-match results

49997dc

change score to 0/1 when matched/not matched, respectively fixes krisk#522

skearney6 mentioned this issue Dec 23, 2020

fix(extended): correctly score include-match results #525

Merged

krisk closed this as completed in #525 Dec 29, 2020

krisk pushed a commit that referenced this issue Dec 29, 2020

fix(extended): correctly score include-match results

443c863

change score to 0/1 when matched/not matched, respectively fixes #522

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

The score is always 1 when using extendedSearch and "include" match type #522

The score is always 1 when using extendedSearch and "include" match type #522

baibonjwa commented Dec 14, 2020 •

edited

Loading

skearney6 commented Dec 23, 2020

The score is always 1 when using extendedSearch and "include" match type #522

The score is always 1 when using extendedSearch and "include" match type #522

Comments

baibonjwa commented Dec 14, 2020 • edited Loading

Describe the bug

Version

Minimal Reproduction

skearney6 commented Dec 23, 2020

baibonjwa commented Dec 14, 2020 •

edited

Loading