[ui] Use hierarchical Route
components instead of manual URL parsing
#2838
Labels
complexity:medium
Something that requires one or few days to fix
kind:debt
Technical debt
priority:medium
Medium priority issues, should only be postponed if no other option
severity:minor
No impact, or minor impact, on live deployments
topic:ui
UI-related issues
Component: ui
Why this is needed:
See #2809 (comment)
Basically, we are only using
Route
to choose which "page" to display, while elements within a page could also benefit from such URL matching rules.What should be done:
Use as many
Route
s as possible, in all pages!Test plan:
Everything should work the same as before (with some bugs removed, if any)
The text was updated successfully, but these errors were encountered: