Improve route configuration (nesting)
We currently have a lot of redundant configurations for routes.
Readability and maintainability could be improved by nesting routes, so we don't need to set data and resolvers for each route individually.
Suggestion:
- Root:
participant
|moderator
|...- Level 1:
room/:id
-> room-specific config here (RoomResolver
, etc.)- Level 2: <sub-view>
- Level 1:
It might be possible to merge the Level 1 routes with the root layer because room roles are always bound to a room. But this would require restructuring of our client URLs, e.g.:
- Root:
/room/:id/:role
- Level 1: <sub-view>
Edited by Daniel Gerhardt