You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It will be OpenAPI compatible so we can generate a base Flutter SDK automatically that we can draw from here.
We will also be upgrading the classic product-opener search to use this backend in the background (with an unchanged API vs what we've already implemented), so we should not deprecate immediately classic search.
We should also implement direct calls to the Elasticsearch endpoint. This will pave the way for a fuller search implementation in Smoothie.
we pass the country as a parameter
=> shouldn't we do so Elastic Search?
we pass app_name as a parameter
=> shouldn't we do so Elastic Search?
we pass the user name in the http header
=> shouldn't we do so Elastic Search?
product structure discrepancies
In the current version
4. the "brands" product field is a comma-separated String, and in Elastic Search it's a List<String>.
=> it probably means that we need a specific new Product class.
Why - Problem description
URL of the doc
https://search.openfoodfacts.org/docs#/
Routes
Schemas
Sub-issues already opened
Related issue in the official mobile app
The text was updated successfully, but these errors were encountered: