searchFloor and search text filter interaction

I’ve recently started a new project with Choices (latest version), and I’m noticing a strange behaviour in filtering.

With a near-default setup:

I’m getting these two sets of behaviour on standard single-choice select boxes:

I managed to narrow it down to the minimum character - based on the above two outcomes (and the fact that other random strings such as zz don’t show any results), it appears to only be searching on the characters above the minimum search length (i.e. + and a)

[ojensen5115]

@lewishowles Choices uses fuse, a fuzzy-matching string search which allows for typos. By default, the fuzziness is very lenient, which can lead to confusing results. It sounds like what you’re looking for is exact string matching.

If you’re looking for exact matching from the beginning of the string, instruct fuse to accept only exact matches by giving it a fuzziness threshold of 0:

var choices = new Choices('.form__select', {
    shouldSort : false,
    fuseOptions: {
        threshold: 0
    }
});

If instead you’re looking for exact matching but from anywhere in the string, AFAIK fuse doesn’t support this directly but you can hack it. Fuse calculates the fuziness of a result as a function of correctness and distance (i.e. offset), so you can tell it to accept a low fuziness threshold and give it a high distance parameter, which causes distance to be weighted very lightly:

var choices = new Choices('.form__select', {
    shouldSort : false,
    fuseOptions: {
        threshold: 0.1,
        distance: 1000
    }
});

Note that if your fields are very long, you may have to tweak the above parameters somewhat.

[DanielRuf]

The solution from https://github.com/jshjohnson/Choices/issues/135#issuecomment-302124496 works. Thanks. Would be good to have this as an example.