JSON API compatibility

[epyx25]

Although the documentation claims that it is JSON API compatible http://ember-graph.com/api/JSONSerializer.html#index, I am having trouble to deserialize a payload

{
  "links":{
    "self":"http://localhost:3001/api/accounts/1?_=1460310632001"
  },
  "data":{
    "type":"accounts",
    "relationships":{
      "roles":{
        "links":{
          "related":"http://localhost:3001/api/accounts/1/roles"
        }
      },
      "company":{
        "links":{
          "related":"http://localhost:3001/api/accounts/1/company"
        }
      }
    },
    "id":"1",
    "attributes":{
      "is-admin":true,
      "username":"admin",
    },
    "links":{
      "self":"http://localhost:3001/api/accounts/1"
    }
  }
}

I am getting the following error

Error: Cannot find model class with typeKey: links

If I remove the links in the deserializer

export default EmberGraph.JSONSerializer.extend({
  deserialize: function (payload, options) {
    console.log(payload);
    delete payload.links;
    return payload;
  }
});

Then it complains about the data property

Error: Cannot find model class with typeKey: data

They are both valid parts of the JSON API specification. http://jsonapi.org/format/#document-top-level

PS.: There is always a parameter added by EG to the end of the requests:

_=1460310632001

Where does it come from, and why?

[deleter8]

EG's interpretation of the json-api spec might be a bit liberal, utilizing guids rather than full / partial urls. It expects a slightly different format for get requests, rather than "data":{"type":"accounts", ...} it expects "accounts":[{account1}, {account2}, ...]. It also implements a variation on updates that more explicitly handles adding, removing, and replacing items in toMany relationships.

As far as the extra parameter added at the end, it's a cache-buster to ensure that it is not stale data from the browser, etc. cache. There is an option to turn that off if it is causing problems.

[gordonkristan]

Ember Graph is (mostly) JSON API compatible, if you look at the JSON API as it existed in the summer of 2014. 😉 The JSON API really picked up steam since then and we haven't kept the adapter up to date. That's something I wouldn't mind tackling given some time (and the need for it).

That being said, writing your own adapter (and serializer) really isn't too difficult. You could probably write one customized for your API in 2 to 3 days. If that's something that interests you maybe I could start the documentation there?

[epyx25]

@gordonkristan We decided to finish our current project with ED.

You could probably write one customized for your API in 2 to 3 days.

Looking at the source code https://github.com/stingerlabs/ember-graph/blob/master/src/serializer/json.js it is defiantly doable, but I would be nice to have it supported, out of the box. ;)