graphefruit
Link flavor profile with tasting view
Instead of having 2 different systems for flavor input (one in bean configuration and another in bean submenu tasting), there could be one.
So, raw text input for flavor profile could be restricted and there could be same menu that is opened when you open "tasting" menu instead with chips style flavor cards.
Then tasting submenu could either be eliminated completely or it'll just change entries used in "flavor profile" field.
However, there could something I am missing here, like "flavor profile" and tasting could serve different purposes. E.g. "flavor profile" intended to be a thing that vendor provides and "tasting" is something that you fill according to your own cupping data.
In that case "flavor profile" and "tasting" can't really be merged but it's still be handy to have suggestions for flavor profile instead of entering data manually.
Hey @gudvinr, thanks for the ticket. Actually the "flavor profile" on beans is just a free-text field, because it 'links' to the descriptions of the roasters. Which could sound like "nut sweetness", which you would not find on any tastingwheel.
The cupping section on beans was a feature request from a user, which wanted to cup/taste the beans, without doing a brew explicit for it.
Maybe there will come time, to link the cupping section aromas to be selectable in the brew-textfield. But thats nothing for now and won't come in a mid-future actually.
