Make matches work with numerical value

[Thearas]

Pull Request

What does this PR do?

Implement #1883.

I have test this PR with unit test. It appears to be working properly:

PTAL @curquiza

PR checklist

Please check if your PR fulfills the following requirements:

• Does this PR fix an existing issue?
• Have you read the contributing guidelines?
• Have you made sure that the title is accurate and descriptive of the changes?

[MarinPostma]

I find it weird that we partially highlight a number. I think a number should be considered as one word @gmourier @curquiza

[gmourier]

I find it weird that we partially highlight a number. I think a number should be considered as one word @gmourier @curquiza

We should keep the same behavior as on a string where MeiliSearch does not match the whole word as well. The highlighting feature consists of having markers to guide the user's eye into the details. I'm not convinced by having different highlighting behaviors between "types" as the default behavior since it could create more confusion in the end than being really helpful on a frontend side.

On the other hand, we could give the possibility in the future to define the behavior of the highlighting feature e.g. fully highlighted, or even how string or number values could behave in case of partial highlighting.

[curquiza]

It works!

Thanks for the PR @Thearas

⚠️ We need the @MarinPostma's review before any merge :)

[ManyTheFish]

Hello @Thearas @MarinPostma!

This PR should fix the issue, thanks!
However, we know that will not highlight numbers perfectly, mainly because of the behavior of our current tokenizer.
We don't have the time to enhance the tokenizer before the beginning of 2022 and an issue with the label good first issue has been opened for this.

thanks again for your contribution!

[MarinPostma]

thank you for your contribution :)

bors merge

[bors]

Build succeeded:

• Run Clippy
• Run Rustfmt
• Tests on macos-latest
• Tests on ubuntu-18.04
• Tests on windows-latest