I have a use case where some menu options have options. I am unable to create a tree of options such that I get a clear understanding of what the customer wants on their plate.

For instance, one of the options for a plate of food is to choose the sides desired. Some of the sides have options with them. The only way to communicate with the user is to ask them to leave a note about how they want their side, with or without sauce, etc.

    5 months later

    Maybe an extension that lets you select required sides but the interface for it would be tricky.

    It’s definitely extension territory rather than core though.

      So, for a sandwich, the options on the sandwich include meat, bread, sides, condiments, sauce. The option values for meat are brisket (chopped or sliced (default)), pulled pork, ribs or sausage. The options for sides are Mac & Cheese, Potato Salad, Shredded Cabbage & Carrots (lime wedge and/or bbq sauce), Green Beans, etc. The options for bread include Regular bun, Jalapeno Cheese bread, Tortilla or slider)

      For the most part I have solved this problem, but not 100%.

        ryanmitchell Couldn’t the code simply build the list of sub-options if the option has children? Add those values to the view enclosed in their own tag indented slightly that you can make visible when the user selects the option that has children?

        Sounds simple, but might be a lot of work. Not sure.