chrisfarber
Rethink the controllers approach?
I love this addon and think it's great. Integration only took 2 minutes. Then in my project I wanted to add a dynamic document title, which very strongly correlates to the final breadcrumb. If I have "Edit post" as the final breadcrumb then I would also like "Edit post" in the title. (Also the same dynamic segment, "Edit Hello world" if the post was called "Hello world")
I found this addon that does that: https://github.com/kimroen/ember-cli-document-title
But they want the title logic in the Route. I think it makes sense because to put it in the Route because it sets up the model anyway. And it seems to be the way forward with the whole pods and routable components approach ember is moving towards. At least it would be nice to have a choice where to put it. What do you think? I'd be more than happy to make a pull request if you think it would make it in to master.
If not please forgive me, I'm kinda new to Ember!
That's a good point point – it seems like the breadcrumb info may need to be moved out of the controllers to be compatible with future versions of Ember.
I'm not sure yet what the right approach is. Personally, I'd like to see what routeable components look like, in practice, before I decide what approach to take. I will say I don't love the concept of putting this info on the route, because routes don't keep a reference to the model object by default.
+1 on this, since the intent is Ember will deprecate controllers. Perhaps a way to support both, with the roadmap to remove controller support?
Any chance that these could be added to the routes themselves? Use this as a mixin to the router so you define the bread crumb with the route?
