JSON-API + new serializers

[tstirrat]

Minimizes the footprint of code by using as much of the underlying JSONSerializer methods as possible.

The main point of difference between the inherited code is how hasMany relationships are stored.

Also uses EmbeddedRecordsMixin for embedded record processing. This will mean that setting the embedded option in the models/* files will be deprecated. The new way forward will be to use a per type serializer with embedded: 'always' as seen here

Merging #282 into this one while we iterate.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

[tstirrat]

Even 2.0.0-canary passes ✅

Just needs the embedded records stuff fixed up and we're good to go.

[tmayr]

Nice! I've tried looking at the embedded records but it goes way over my head, will keep looking!

[tstirrat]

I've decided to make new models specifically for the embedding, trying to override embedding stuff inside each test was too cryptic and problematic.

Should have something working by end of day :)

[tstirrat]

Waiting on emberjs/data#3550

[tmayr]

Oh wow, that was way more complex than I thought, glad that it's being resolved soon!

Is there any other change left for either #267 or 2.0 compat milestone?

[tstirrat]

Yeah, the way the new serializer stuff works you don't have access to the records anymore (it's for the best) .. but it sure made things a little crazy in the adapter :/

[tstirrat]

This will get us compatible with both 1.13.x and 2.0-canary

If you want to help out any more, we could do with some more testing to work out if there are any edge cases in the embedded records stuff. I have tested the "basic" example for embedded records, but there could be things like when there are relationships defined in both directions i.e. parent hasMany children where children define child belongsTo parent.

Or just check out this branch, pair it with branch in emberjs/data#3550 and try a few things out with it (not necessarily embedded stuff)

Tests in general will always be helpful in getting us over the line when 2.0 stable launches. Some of the new methods I wrote in the adapter need some checks and balances.

And finally I do want to eventually move the recordWillDelete code into the ember data standard deleteRecord handler.

[tstirrat]

Disabling embedded tests so that I can make an early release. the embedded stuff will need to wait for emberjs/data#3550

[tmayr]

Might give a try to updating to Ember Data 1.13 later using this branch, will let you know if everything goes smoothly.