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
Is your feature request related to a problem? Please describe.
Depending on recipe, but sometimes for the same recipe, it is useful to see nutritional information both per serving and per 100g.
It would be useful to be able to add both calculations to the same recipe.
For instance, it is always good to see how much a serving according to the recipe is, but if keeping track of calories and macros, then the weight is of more importance.
Describe the solution you'd like
Add tabs to the nutritional information section for viewing/editing both per serving and per 100g values for the same recipe.
Ideally the nutritional calculations would still work for both of these values, but an easier first implementation could be that only one of these tabs gets populated, using the current implementation calculating/setting the nutritional values during scraping.
To make it easier for the end-user to fill in the values for each tab, there should also be a function to copy/move values between per serving and per 100g, e.g. if the automatic population of the fields have incorrectly set the per serving tab, then the user can click a button to move all values to the per 100g tab instead.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Depending on recipe, but sometimes for the same recipe, it is useful to see nutritional information both per serving and per 100g.
It would be useful to be able to add both calculations to the same recipe.
For instance, it is always good to see how much a serving according to the recipe is, but if keeping track of calories and macros, then the weight is of more importance.
Describe the solution you'd like
Add tabs to the nutritional information section for viewing/editing both per serving and per 100g values for the same recipe.
Ideally the nutritional calculations would still work for both of these values, but an easier first implementation could be that only one of these tabs gets populated, using the current implementation calculating/setting the nutritional values during scraping.
To make it easier for the end-user to fill in the values for each tab, there should also be a function to copy/move values between per serving and per 100g, e.g. if the automatic population of the fields have incorrectly set the per serving tab, then the user can click a button to move all values to the per 100g tab instead.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: