-
Notifications
You must be signed in to change notification settings - Fork 72
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
Why does Waistline import ingredients and traces from OFF? #412
Comments
Yep let's drop them. I think I added support for importing them when I added support for uploading them, but can't really see a use for it. I don't think we need allergens either. Might also be good to remove the uploading of ingredients and traces too since I think the app should keep its focus on calorie/nutrition tracking. |
@davidhealey Allowing Waistline users to at least take a photo of the ingredients would be hugely beneficial to the project. Wording it like "Help Waistline's datasource by sending a photo of the ingredients" could set expectations right. |
Maybe we could have an additional images section. |
For a while now, when importing food items from OFF, Waistline also imports the
ingredients_text
andtraces
fields. I would be interested to know why it does that. As far as I can tell, this information isn't used for anything. But especially theingredients_text
can take up a lot of valuable storage space in the local database.If this is about food intolerances, I think it would make more sense to import just the
allergens
field instead of the wholeingredients_text
.Otherwise, maybe we can drop these fields altogether?
The text was updated successfully, but these errors were encountered: