We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Häagen-Dazs
Hi everyone!
In the app, we use the autocomplete feature to list brand names. But there is an issue with accentuated characters (e.g.: with "Häagen-Dazs").
When we call the autocomplete method, with Haa as a query, it never suggests Häagen-Dazs. Is there a way to bypass the strict matching?
Haa
The text was updated successfully, but these errors were encountered:
Is there a way to bypass the strict matching?
I suggest you forward that issue to https://search.openfoodfacts.org/docs#/default/taxonomy_autocomplete_autocomplete_get because even with a "fuzziness" of "2" (default is none) we cannot transform ä into a (looking for brand in en).
ä
a
brand
en
Sorry, something went wrong.
Is there a way to bypass the strict matching? I suggest you forward that issue to search.openfoodfacts.org/docs#/default/taxonomy_autocomplete_autocomplete_get because even with a "fuzziness" of "2" (default is none) we cannot transform ä into a (looking for brand in en).
I suggest you forward that issue to search.openfoodfacts.org/docs#/default/taxonomy_autocomplete_autocomplete_get because even with a "fuzziness" of "2" (default is none) we cannot transform ä into a (looking for brand in en).
Ok, I will open an issue on the dedicated repo 👍
No branches or pull requests
Hi everyone!
In the app, we use the autocomplete feature to list brand names.
But there is an issue with accentuated characters (e.g.: with "Häagen-Dazs").
When we call the autocomplete method, with
Haa
as a query, it never suggestsHäagen-Dazs
.Is there a way to bypass the strict matching?
The text was updated successfully, but these errors were encountered: