Your application needs user settings. You need to persist some sort of structured data that decides how the application should function. This is a common use case. Ember-Data (shockingly depending on who you are) makes this easy.
Here are some assumptions:
* You have POST /settings as well as GET and PUT routes.
* The server just saves whatever data is sent w/o any processing or other handling.
* There may be any number of complex objects representing settings.
It's easy to begin.
Your new post is loading...