Take the example seen here. https://ember-admin-dashboards.herokuapp.com/
It shows a dashboard of mutiple data soruces that are consumed to generate a single page. I need a format similar to this for my app. And while this example does a great job laying out the routing and formatting it doesn’t show the data (as it uses websockets.io in a controller for the twitter stuff, and the rest is dummy data.
So lets take a single example. In the header you can see badges indicating how many messages a user has. Building the back-end API for that is simple, and I understand how to call the API using ember-data. But all the examples I have seen and documentation I have read show that Ember recommends populating your model objects in the routes class which seems to be tied to a URL. I wouldn’t think i would want each route defined in the app to re-call the API needed for that badge (even if in a parent function/class way).
So what’s the correct way in Ember to have the main window populated based on the URL, but have the data retrieval in the header be dynamic as well?
Does the question make sense?