Routing: Analysis

[kategengler]

• goal: to use <template> tag in routes

• goal: not needing controllers

• goal: route-based tree-shaking (currently accomplished by Embroider shipping its own version of the router but these should be combined)

• goal: query params easier to use by default (maybe even not even need to be configured?)

• [ ] make the route/router pluggable so we can iterate on the API outside of ember source. if someone wanted to work on this, it should be kept rather bounded/tightly scoped.

• [ ] identify: what capabilities do we actually need for the route class?

• [ ] write an RFC, or series of RFCs to cover the necessary steps (if experiments are successful)

Notes:

• https://wycats.github.io/polaris-sketchwork/routing.html

1/22/24: Potentially waiting on reactivity dicussions

[kategengler]

Being scoped down for Polaris. Spec spoke about it on June 6. Maybe we can serialize convo here a bit?