1,082
edits
Nutrients handling in Open Food Facts: Difference between revisions
no edit summary
No edit summary |
|||
| Line 69: | Line 69: | ||
** It removes unnecessary conversions from kcal to kJ and back (which is not trivial, as some people/apps may choose a different conversion factor, such as 4.2 or 4.185) | ** It removes unnecessary conversions from kcal to kJ and back (which is not trivial, as some people/apps may choose a different conversion factor, such as 4.2 or 4.185) | ||
** This would be a breaking change if some apps use the energy-kcal_100g/serving or energy-kj_100g/serving fields | ** This would be a breaking change if some apps use the energy-kcal_100g/serving or energy-kj_100g/serving fields | ||
== Possible improvements to make thing (a bit) more complex == | |||
The current API does not allow to store values for the prepared product, but it can be done on the OFF web site. | |||
We should extend the API to allow to write nutrition facts for the prepared product. | |||
The fields for the prepared product are the same than for the as-sold product, except "_prepared" is appended to the nutrient-id. | |||
e.g. saturated-fat_prepared_100g, saturated-fat_prepared_value etc. | |||