Skip to content
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

serving_quantity_unit is not returned if there is a space in Serving Size between the size and the unit. #11015

Open
theedov opened this issue Nov 14, 2024 · 0 comments
Labels
API READ All READ APIs include Product, Search… API Issues related to the Open Food Facts API. More specific labels exist & should be used (API WRITE…) 🎯 P1 serving size

Comments

@theedov
Copy link

theedov commented Nov 14, 2024

What

If someone updates the product serving size to contain a space between the size and the unit, it makes the API not return the serving_quantity_unit.
For example, if I enter "5 g”, there will be no serving_quantity_unit returned from the API, but if I enter "5g”, everything is ok, and serving_quantity_unit is there.

Steps to reproduce the behavior

On the web, try to edit "Serving Size" of any product to contain space between the size and the unit.

Expected behavior

The response should have serving_quantity_unit returned in both scenarios(or maybe consider not allowing spaces).

Type of device

REST-API

@github-project-automation github-project-automation bot moved this to To discuss and validate in 🍊 Open Food Facts Server issues Nov 14, 2024
@teolemon teolemon added API Issues related to the Open Food Facts API. More specific labels exist & should be used (API WRITE…) API READ All READ APIs include Product, Search… labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API READ All READ APIs include Product, Search… API Issues related to the Open Food Facts API. More specific labels exist & should be used (API WRITE…) 🎯 P1 serving size
Projects
Status: To discuss and validate
Status: To be triaged
Development

No branches or pull requests

2 participants