primaryData key during deserialize in JSONAPI source

[jakubrohleder]

Hi! I'm testing a sample app using angular.js and Rails backend using jsonapi-resources. Unfortunatelly I've encountered a problem during data synchronization:

Deserialize method in JSONAPISerializer uses [resourceType] as a key for primary data, while in my server response (as well as in jsonapi specification), primary data appears under a top-level key named "data".

Is it somehow my fault, or it should be that way?

[dgeb]

Sorry for the inconsistencies with jsonapi-resources, and the JSON API spec itself.

I'm working on bringing the JSONAPISource up to date with the spec this week, and will be tracking progress via #113. My goal is complete compliance by the JSON API 1.0 release date - May 21.

[pixelhandler]

@jakubrohleder @dgeb yeah I ran into that as well. I created a blog api here using the JSON resources gem - https://github.com/pixelhandler/blog-api/ the client app needed some workarounds in the JSONAPISource like so https://github.com/pixelhandler/blog/blob/master/app/adapters/application.js https://github.com/pixelhandler/blog/blob/master/app/adapters/application.js I'd be willing to contribute updates to the JSONAPI Source/Serializer if needed. (could pick this up this Friday)

[dgeb]

This should be addressed via #156.

Sorry for the delay in reaching JSON API 1.0 compliance.