I’m at the early stages of building a SaaS app. I want it to be 2.0 ready with minimal refactoring. As such I’m building along the lines of : Future Proofing Your Ember 1.0 App
Problem is I’m finding nothing is gelling that well at all and frankly it feels a bit fragile while we span this not-quite-2.0 status of minimally implementing controllers and eliminating views.
The problem is, if like Google’s Material Design components, you consider components to be totally self contained and unaware of the context in which they are to function, you can’t very send data down from the route (or controller if you’re using them) and actions back up into the route (or controller). Because the component won’t be portable, it’s now dependent and therefore not as reusable as I understand a web component is supposed to be.
For example, if I have a dynamic navigation component, should it not load the links to iterate directly? If it were me, I’d prefer to have the component use the store to load the model and iterate directly. And if the user re-sorts the nav or adds/removes a link, marks as a favorite, … should it handle this interaction directly within the component (or possible sub-component). I mean, if we are totally breaking the MVC pattern, why not go all the way?
Perhaps there is some unexpected impact on the lifecycle or rendering that I’m not aware of (eg loading routes … ?)
Would appreciate comments/feedback.