Can someone provide a practical example of what a “routable component” would look like? Concept seems really alien to me.
I have read the Road to Ember 2.0
A few questions:
1.) Will the component ever be implicit?
say I have
Will that mean that a generated component will exist?
And I only have to define a template. Presumably the component will need to be explicitly defined in the pods folder along side the route file.
2.) Will there be the concept of a singleton component or is that really just a service?
3.) If not singleton how will we know which instance of the component to pass the
4.) Will there be a set up component method in the route or any kind of analog to setup controller? Where will initialization logic live?
5.) Can a route conditionally load different components depending on the some variable or state of the models in that route? In other words how tightly bound will a given component and a given route be? Is it logical for a route to back multiple types of components, or even multiple instances of a specific component type. The latter case seems like it might be an interesting way to provide a buffer state. Multiple phases of a route expressed by multiple instances of a component as the model is mutated. Perhaps a convenient way to manage undo and rollback.
6.) Other than user confusion were there any other technical reasons to abandon controllers?
Probably more to come when someone posts the RFC. But just curious what people’s early thinking is on this topic.