Nested routes with multiple params and Outlet: /organizations/$orgId/teams/$teamId

[sachingaikwad123]

I have created a 'Outlet' where following routes will be rendered:

/organizations/list:

• It shows list in 'Outlet'
• Shows list of Organizations (Name)

/organizations/$orgId:

• It replaces 'outlet' with Organization Details
• Shows details of 'selected' Organization.
• It also shows 'list of teams' in a tab (route change not required for this)

Question:

/organizations/$orgId/teams/$teamId

• I want route path in URL to show to this when user clicks on any "Team" from list. Because this represents the hierarchy: Organization and then team within it.
• But, now I want 'Team Details' to be rendered in same 'Outlet'. That means, I want 'Organization Details' to go away and only 'Team Details' to show up. But, if I understand it correctly because of $orgId, 'Organization Details' component will be rendered, right?
• How to achieve what I want?
• Also, I do want $orgId param to be available in 'Team Details' component

Q: Is this possible to implement in TSR?
Q: Is this good approach to keep routes in my application or there is something fundamentally wrong in the approach of route arrangements itself?

[sachingaikwad123]

Do I need to define $teamId route file path like this: /organizations/$orgId_/teams/$teamId

Adding "_" after directory name of $orgId to un-nest this component? But will it keep $orgId in the route path and pass $orgId in "params" for $teamId path?