Help wanted: JSON:API

[okuramasafumi]

On jsonapi branch I'm developing a JSON:API compatibility but there's an issue.
It's hard to confirm Alba is actually compatible with JSON:API. There's no test suite so I copied some specs from https://github.com/jsonapi-serializer/jsonapi-serializer but we need more specs.

Could anyone add some specs for JSON:API?

[jrochkind]

Is it helpful to realize there's a JSON:API JSON Schema, and you could use the ruby json_schema gem to validate any JSON against the JSON:API JSON schema? (Although to be fair, json:api FAQ says "Validation will not yield false negatives, but could yield false positives for the sake of flexibility.")

That might be one way to verify that any given output is legal JSON:API, although there may be more to verifying compatibility than that.

I am definitely interested in json:api support here. Looking at the diff between your branch and master, I haven't quite wrapped my head around what's going on.

Can you say more about where you are stuck, or if there's any way for anyone else to help?

I would also be interested in the possiiblity of using the same serializer to serialize as JSON:API or "plain", not sure if that's feasible or not.

[okuramasafumi]

I am definitely interested in json:api support here. Looking at the diff between your branch and master, I haven't quite wrapped my head around what's going on.

Thank you, what I want to achieve is to use Alba's existing functionalities as much as possible. JSONAPI module "inherits" from Alba::Resource module and expands its functionalities.

Can you say more about where you are stuck, or if there's any way for anyone else to help?

I got stuck due to the lack of "official" specs that ensure Alba is compatible with JSONAPI. I think it kinds works now, but will have many problems when it goes production.

[ngouy]

What do you think of having a list/table of features that JSON:API "requires", then having 2 columns:

• specs available: we have made some specs that fits 100% what JSON:API is asking for
• supported: we made the code to make column 1 happy. So we can say feature x is supported

And at least from there we could know how far we are, or what coverage we have for supporting JSON:API specs