Setting up an Ember project from scratch that works with `resources` is a bit convoluted

[sergiofenoll]

For a small bug reproduction I setup a new project with a custom frontend from scratch using mu project new project-name and edi ember new frontend-name. After wiring everything up I couldn't get resources data in the frontend and was hit with a confusing error: You tried to push data with a type 'agents' but no model could be found with that name.

After cross-referencing the setup in Kaleidos I realized I needed to set the default application serializer to JSONAPISerializer. I probably would've also found it if I went to check the Ember documentation, but I'd have to know by heart that it's related to the serializer.

I wonder if instead we could add this to whatever README/tutorial is presented to people creating an Ember app for a semantic.works stack? Perhaps we could even add a mu frontend new command to mu-cli that wraps ember new and adds the default stuff needed for our stack to work?

[sergiofenoll]

From @erikap in a Rocket.Chat discussion:

for people running into the same error in the future
edi ember g serializer application

Perhaps we could add this to the README of https://github.com/mu-semtech/mu-project or the output of mu project new app-NAME.