#community-help

Exclude Typos in Numbers with Typo-Tolerance Parameters

TLDR Jan inquired about excluding typos in numbers using Typo-Tolerance parameters. Jason suggested creating a feature request on GitHub and mentioned that turning off typo tolerance for a specific field is possible.

5mo

Join the chat

Jun 19, 2023 (5 months ago)

Photo of md5-79fc728f0635dc2218142cb603ce2570

Jan

02:52 PM

Hi!
Is there a way to use the Typo-Tolerance parameters that will exclude (not tolerate) typos in numbers?

For example, looking for a specific case number in a project archive should alway match exactly the number entered in the search.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:26 PM

We don’t have a way to prevent typo tolerance for numbers. Could you create a GitHub issue with this feature request?

But if this value is in a separate field, you can turn off typo tolerance just for that particular field

04:26

Jason

04:26 PM

See 3rd paragraph under num_typos in this table: https://typesense.org/docs/0.24.1/api/search.html#typo-tolerance-parameters

Jun 20, 2023 (5 months ago)

Jan

11:24 AM

Thanks for your reply. I’ll create a feature request!

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3011 threads (79% resolved)

Join Our Community

Similar Threads

Discussion on `num_typos` String-Type in Libraries

Denis queried about `num_typos` string in libraries. Kishore Nallan clarified its usage for disabling certain fields.

20mo

Discussion on 'strict' search and typo-tolerance

A and James queried about 'strict' search and typo-tolerance settings. Kishore Nallan and Jason clarified that these features are configurable and an upcoming release will enhance this.

32mo

Discussion on "num_typos" Feature Implementation

Stefan inquired about an upcoming feature. Kishore Nallan confirmed its recent implementation and promised to upgrade Davide's cluster if needed. Davide expressed appreciation.

32mo