New: No Exact Match

Better Context

We just added a new feature to our Search endpoints:
`no_exact_match: true`.

This data point will be returned when a user searches for part of an SKU or a semantic phrase like "something I can use to train my dog", where there is no exact match for any products.

Clerk already predicts which results to show regardless of how a user serches, but with this small feature developers can easily add extra context in the search function, like "We couldn't find an exact match for 'fidge' but we found these close matches".

This feature will be added as a standard to all Omnisearch designs.