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
I have searched the existing issues and nothing seems to be related to my idea.
Is your feature request related to a problem? Please describe. What is your idea?
Ingredients differ in taste and resulting recepts. You have the same cocktail, but with ingredient A you need more and Ingredient B needs and additional Ingredient. It would be greate to enable links between cocktails, like variants, so get able to see "with Ingredient A it gets smoother in taste" and with "Ingredient B it gets more fruity or stronger".
Describe the solution you'd like. How should it look in the app?
1. Copy and Linking
Copy the existing Cocktail and add a link between them -> if you open one, you could see other variants
Technical this could be easily resolved with an CocktailRecipeGroup - Table (groupId, cocktailId, variantSpecial)
2. Variation of the existing
Create the oportunity to modify an existing with variants in the same recipe
Technical no ideas how this could be solved
During the writing of this issue i personaly prefer the 1. Method, but its not well thought out
Anything else? (Additional Context)
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is your feature request related to a problem? Please describe. What is your idea?
Ingredients differ in taste and resulting recepts. You have the same cocktail, but with ingredient A you need more and Ingredient B needs and additional Ingredient. It would be greate to enable links between cocktails, like variants, so get able to see "with Ingredient A it gets smoother in taste" and with "Ingredient B it gets more fruity or stronger".
Describe the solution you'd like. How should it look in the app?
1. Copy and Linking
2. Variation of the existing
During the writing of this issue i personaly prefer the 1. Method, but its not well thought out
Anything else? (Additional Context)
No response
The text was updated successfully, but these errors were encountered: