@boyanyordanov wrote:
Hello!
This is my first post here, I tried to research as much as possible and didn't find anything like our use case and after a few days of experiments I decided to move the conversation here.
So we have a part of our application what consists of a couple of lists displaying nested data and a form for editing. A simple recreation:
The first column has a list of groups, the second has a list of items that can be assigned 0, 1 or more groups and the form in the third column is used for editing an item or to create a new one.
I realise that this is a bit too specific but the concept can be applied for other scenarios.
Whatever I do I can't escape the need of loading the models for the first two columns multiple times with
RSVP.Hashand copying layout code around instead of using{{outlet}}for the nested routes.For example
- the route listing all items, should also list the groups, but there's no logic in nesting them in this case
- the route listing the items of a group, on the other hand can easily use nesting
- and then there's the form which has two states for editing and creating an item, but with this structure it also needs to display the groups and items and mark which are selected.
Posts: 3
Participants: 2
