RSVP.hash will still create 3 root keys so I think I would setup 3 models on the fourth route. If the information in the 3 models is exactly in the same structure and you want to squash them in one array I think you need to use Ember.computed to create it.
If you build out an example ember-twiddle, it might be easier to see the specifics of your use case and offer an alternative. There are many times where I want a ‘dashboard’ type page that includes all my models - but there is this “don’t use RSVP” attitude out there and no other ember-approved solution. In theory, we’d have components with each model - right?
thanks @sheriffderek I did see that Ember Igniter article in my initial attempts to solve my problem.
I have tried to make an Ember Twiddle but I’m new to this and I can’t get it to work without it giving me a thousand errors in the console. But hopefully it gives you an indication of what I am trying to achieve.
If it needs editing / updating please let me know and I will try again
OK. This is a good example of why the twiddle is helpful. Your errors are because of how you’ve thought through the resource. What it wants is a model like ‘thing’ in singular and then to iterate through ‘things’… so it’s confused and looking for thing3s because ember-data is pluralising what you’ve given it. I’ll look at it more thoroughly when I can…
‘thing’ is great, but a real-world example might be easier to work with.
(ember-twiddle is great, but I also know that renaming things and reworking file structures is not very smooth - so it’s best to move one step at a time and just do it once, instead of putting it all in there and allowing the errors.)
Take a look at this and see if this is in the right direction: Ember Twiddle
This mostly makes sense to me. I think the part I really can’t understand is the getting the players to list out in the template. From looking at your example I think they should but they don’t and they get logged in the console.
{{log something}} was a great tip tho! I had often wonder how I could console.log things so thanks!