Create "Select Option" area on menu item page

[brunorplima]

Some items from the menu need to have options for the user to choose from to specify to the admin what he wants. For example, Refrigerante might be Coke, Sprite, Guarana etc. There is already a model in place that handles that, the MenuItemOption and the MenuItemModel is associated with it by the optionIds property.

Requirements:

• [x] It should follow the same style of "Escolha seus Adicionais".
• [x] For menu items that have options associated with them the add item button should be disabled until the user selects one of the options. Options are supposed to be information needed by the admin user hence it should be a required field.
• [x] Only one option among all the options should be allowed to be chosen. By selecting another option after the user's chosen an option before, the option previously selected should be unselected.
• [x] An option may have an extra price, so make sure to add logic for handling the addition of the option's price to the total price of the item.
• [x] Add additional information between this new area heading and the first option saying "Escolha obrigatória" or something similar if it reads better. Make it smaller than the heading and option name font sizes.

[ericbraz]

Já estou alterando o código pra exibir essas outras opções, mas verifiquei que um dos itens tem essa propriedade. Essa propriedade será usada?

[ericbraz]

English, sorry. I also realized that MenuItemOption interface had no canBeExtra property:

But I found this property in DB:

A few items have it

[ericbraz]

Since this items shall be displayed separately from other items, nor as aditions to a promo with a drink (in example) I think they don't have to be single choice.

[brunorplima]

Já estou alterando o código pra exibir essas outras opções, mas verifiquei que um dos itens tem essa propriedade. Essa propriedade será usada?

No, this property was being used before but it was changed. When we need to make changes on the db structure because we don't have a MVC framework to do db migrations for us it's possible that old things like this uniqOptions might still be found in the database. You shouldn't take the database as reference, but the models instead. You will see that in the MenuItemModel this property doesn't exist, so you won't be able to use it (even if the db returns a document with this property there). The property you'll use is the optionIds if I'm no mistaken.

[brunorplima]

English, sorry. I also realized that MenuItemOption interface had no canBeExtra property:

But I found this property in DB:

A few items have it

Same as before, take the interfaces and models as reference, not what's on the database, because what is not in interfaces/models is never gonna be saved on new items anymore. It was deprecated. Likewise, if you try to use menuItemOption.canBeExtra in the code you'll see a compile error thrown by typescript, because it can't access a non-existent property of MenuItemOption.

[brunorplima]

Since this items shall be displayed separately from other items, nor as aditions to a promo with a drink (in example) I think they don't have to be single choice.

They have to be a single choice, because you can't buy a pop that is both a coke and a sprite. They can go with a promotion, if they want to create a combo they only need to create a new menu item with name hot dog + refrigerante, add this on the description and add options such as Coca cola, Sprite and H2O. The idea behind options is not to be an addition to an order, instead is to give further information to the admin users of what drink flavor/option that person wants, instead of just saying he wants a drink.

I agree that there is a limitation in our db structure to easily allow admin user to create combos like creating a menu item that references other menu items, but maybe that's something to worry about when they decide they want to pay us to improve that. We can talk more about this later on.