New to the community, hello hamsters!
Wondering if anyone can provide some history about Ember’s decision to default to the JSONSerializer. I know this became the default with version 2.0, and REST had been the standard before then, and that there are ways to override it in a particular application.
Really interested in understanding what drove the decision. I come from the Drupal community, where there are some challenges to creating some of the JSON structures described in the Ember docs. Talking about things like relationships and included keys here, which could be a challenge to support in a meaningful way.
From what it looks like on the outside, the goal is to make data loading ultra efficient, where models line up exactly with the keys in the JSON response and developers don’t really need to worry (too much) about data on the application level. Is this really the goal, or am I reading it wrong? Is this really what an Ember developer expects from an API, that kind of control over the structure?
Would love to hear everyone’s thoughts! Ember Data is fascinating and I am really enjoying learning more.