Analyse JSON API Version 1.1 RC 1

[sliverc]

New release candidate of JSON API specification has been released.

There is now also a changelog to be reviewed at https://jsonapi.org/#update-history

A quickly browsed through it and it seems a few small changes would be needed to be done in DJA.

Opening this issue as a task to analyze what single steps needs to be done in DJA to support 1.1. Best is to open a new each for each single task.

[n2ygk]

@sliverc Thanks for following these updates with JSON API. I've reviewed the release notes and created an issue for each item. Note that it is not yet a release but a release candidate, so there's always some chance there will be further changes before the official release. Now is a good time to review these and see what work is required. The planned release date is January 31, 2019.

Should I create a milestone to track this? We don't necessarily have to include all these items in a new release though....

[sliverc]

from jsonapi.org:

JSON:API v1.1 RC1 has been published! Please review and try out this upcoming version of the spec before its planned release date of January 31, 2019.

Keeping this in mind we can discuss the different issues in its respective issue. If there are still questions concerning specification we should raise it to the jsonapi.org in time. After this deadline has passed I guess we can implement the different issues as time permits (without having a milestone).

[auvipy]

we can start work on this now

[sliverc]

Even thought the date has passed long ago version 1.1 has not officially been released yet (hint still set on https://jsonapi.org/)

But of course it would be good to get started with those issues if someone has time at hand as the spec won't change much from what it is now.

[auvipy]

any suggestions for me on how can i update them in current code?

[sliverc]

#553 might be an easy one to start with.

[n2ygk]

FYI - JSONAPI 1.1 has reverted to a working draft so hold off on any implementation work. See json-api/json-api#1403 (comment)

[sliverc]

Interesting what's happening with the spec. I guess we have enough tasks at hand anyway so can easily wait... 😄 it seems though the spec might mainly change around profiles though.

[sliverc]

@n2ygk
It seems like the JSON API spec 1.1 won't be released anytime soon. There are now quite a few 1.1 issues cluttered in our database which we cannot really resolve. I would prefer we close them and once it is clear what to implement we can always reopen them again. What do you think?

[sliverc]

Closing as explained at #547 (comment)

Once JSON API spec is moving forward we need to double check which issue need to be reopened.

[auvipy]

• 2020-08-20: 1.1 Release candidate 2 released.
  • Extensions were added and the
    scope of profiles were reduced
    since their introduction in RC1.
  • Links can be represented
    as RFC 8288-style web links.
  • A new describedby links member
    was added so that implementors can incorporate description documents (e.g.
    OpenAPI or JSON Schema)
    directly into their APIs.
  • Local IDs
    were introduced so that a
    client can create a relationship to a resource yet-to-be created by the
    same request.

[auvipy]

We can re-open this & analyze JSON-API 1.1 RC2 and modify the related closed issues. it seems with new extensions and other overhauls it is not so far from release this time.

[sliverc]

By the experience we had with the RC1 where we put quite a bit of work into analyzing what needs to be done in DJA and then quite a few changes were made again in the specification I suggest we leave this closed till the specification is final. Especially when I look how in 1.1 RC2 extensions are defined it seems this is simply not finished yet.

Once 1.1 is final we need to specifically analyze what needs to be changed in DJA. An issue with a simple link to some feature won't be enough.

I want to encourage everyone to take part in the JSON API specification discussions though and think through it there.

[auvipy]

I do follow the modifications process and chime in where I feel. this can be opened to get traction IMHO.