Managing 3 levels (or more) deep relations.
Hey guys,
I was wondering how you would handle this business case in terms of UX.
So with 2 levels it's easy. Relation manager on one resource.
Now let's say we have Project, Todo and Comment.
If you still manage Todos of a Project using a relation manager, you would have to change to the TodoResource when you want to manage Comments of that Todo.
It might be a bit bad example, as the chances of an user wanting to manage comments on the projects table isn't very often if even all, but there are other use cases this applies.
So my ideas so far were:
1. Just let the user change resources manually via navbar.
2. Make the edit button link to the resource edit page instead of the the relation manager. Then you can also remove the TodoResource from the sidebar (if that makes sense), as it helps to keep the workflow from creating project -> creating todos -> managing comments clear and straightforward.
3. Using a HasManyThrough relationship to manage comments on the project resource
Now I'm curious about your approaches to this.
1 Reply
Nested resources will be natively supported in v4 in the meantime you can use this plugin https://discord.com/channels/883083792112300104/1167940700130791574 which i have used to manage resources nested to 4 levels deep