The documentation looks like:

But it should look like:

CommentFileSizeAuthor
#2 3000609--jsonapi-collections-fixes--2.patch982 bytese0ipso
2018-09-18 16-11-40.png33.06 KBe0ipso
2018-09-18 16-10-40.png32.7 KBe0ipso

Comments

e0ipso created an issue. See original summary.

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
commented
Status: Active » Needs review
StatusFileSize
new 3000609--jsonapi-collections-fixes--2.patch982 bytes

This is the adjustment.

Status: Needs review » Needs work

The last submitted patch, 2: 3000609--jsonapi-collections-fixes--2.patch, failed testing. View results

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
commented
Assigned: e0ipso » Unassigned

Unassigned.

  • richgerdes committed 4714b4c on 8.x-1.x authored by e0ipso 
    Issue #3000609 by e0ipso: Documentation for JSON API collections needs...
richgerdes’s picture

richgerdes
he/him
Primary language English
Location New Jersey, USA
commented
Status: Needs work » Fixed

Patch looks good, and is fairly simplistic.

Looking at this, I think it may make sense to try to make this an api within schemata (or jsonapi_schema) so that we can limit the amount of schema we are building/altering within OpenAPI.

I have opened #3062582: provide an api for building route response or parameter structure for jsonapi. so I can revisit this idea.

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
commented

@richgerdes Agreed! In fact, JSON:API Schema will give you the full thing for collections and for individuals.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.