Defining Json-API Adapter as Default

[joaomdmoura]

As we decided, it's time to push JSON-API forward by making it the default adapter into AMS.
We really believe this is one of the greatest features into 0.10.x version, and that could help a lot of different projects from different technologies.
Despite of being a small change, we expect to see more people using it's conventions once we merge it.
@steveklabnik @guilleiguaran @kurko

[joaomdmoura]

@guilleiguaran o/

[guilleiguaran]

@joaomdmoura \o

[spastorino]

We would need to revert this in order to be able to use AMS by default in Rails. ❤️

[steveklabnik]

This has changed?

[joaomdmoura]

@steveklabnik we have just talked trough it on IRC.
You can check the conversation there but the idea is to make it easier to integrate with the usual JS frameworks around that are not using json api yet.
Ember is already moving forward with it, but the ideia would be to avoid push it at once but make it really easy to use.

[steveklabnik]

:/

[steveklabnik]

So, basically, the reason that JSON API should be the default is multifold, but one of the main ones is that convention over configuration is the heart of AMS.

You pick some kind of thing as the default, and so choosing an underspecified, ad-hoc old version doesn't make nearly as much sense to me. Classic AMS output was changed in JSON API because it isn't particularly great, a starting point.