Route + route name abstraction

In Ember, there are both. In newer routers, inspired by React Router, neither exist.

The route abstraction adds additional conceptual complexity, but comes with extra functionality, like multiple outlets per route. In the React world (and other routers), it might make it harder to place multiple components in that same way (see: https://github.com/reactjs/react-router/blob/master/examples/sidebar/app.js )

I should think more about this. These thoughts came up while I was working withs sheet-router, which is a pretty barebones implementation.

Read the linked React Router sidebar example and the sheet-router implementation referenced in the issue. First clarify whether route and route-name abstractions are being proposed or rejected, then define a concrete scope and acceptance criteria before implementation; the issue currently provides no files, tests, or actionable completion condition.

Written by the indexing model from the issue text.