-
-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
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
Add a project switcher to search (and store the type on each product opened "off", "obf", "opf" and "opff", and for any search we store locally) #5586
Comments
@teolemon So for the moment the off/obf/opf/opff field isn't stored in the product data (e.g. as 'flavor'), it's just the fact that someone store it and then we found it in off or obf that tells if it's food or beauty, right? I've just found 4056489368793 in both, so what is it supposed to be?
The primary key of the product would become barcode AND flavor? |
|
In your spreadsheet I see duplicates that need to be solved. Using a universal search would be helpful, instead of up to 4 searches, but as long as the barcode is unique among all 4 systems it's not a problem for Smoothie. I assume adding flavor as a product field would be easy to implement - once the duplicates are removed. And it will make life much easier in Smoothie. |
Since openfoodfacts/openfoodfacts-dart#973 we have a
Following are the methods we currently use in Smoothie, that need to be able to switch servers when needed:
|
@stephanegigandet a clue to the ongoing situation with search: Hash Ecoscore |
I think that was solved, have you seen it recently? |
@stephanegigandet Still experiencing an issue in .dev for beauty, but not the HASH issue for beauty in .org:
|
@monsieurtanuki on .dev we only have openfoodfacts.dev, we don't have openbeautyfacts.dev etc. |
@stephanegigandet Then to answer your question: we don't seem to experience the HASH error anymore in .org. |
What
Mockups
https://www.figma.com/design/nFMjewFAOa8c4ahtob7CAB/Mobile-App-Design-(Quentin)?node-id=5816-19916&node-type=canvas&t=1Rms31ZpldZawPl9-0
Part of
The text was updated successfully, but these errors were encountered: