Problem/Motivation

We want to declare what are the implemented extensions in our responses. At the moment we are using the filter strategy (extension pending), and the partial success strategy.

Proposed resolution

Have the format specify the non-negotiable extensions in the response headers. These 2 extensions cannot be disabled and therefore will always be active regardless of the extension negotiation from the client.

Remaining tasks

#2798279: [TASK] Create a JSON API extension for filtering

Comments

e0ipso created an issue. See original summary.

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
commented

We need to create a JSON API extension that describes the way we do filtering, pagination and sorting (maybe 3 extensions?) in the Drupal module (as expressed by #2798279: [TASK] Create a JSON API extension for filtering).

Since JSON API says almost nothing regarding filtering strategies, our goal is to allow someone else to say «I'm using JSON API and "drupal/filtering" with "drupal/sorting" and "drupal/offsetPagination"». So their specification is narrower and they don't have to re-invent (our) wheel.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Actually, such a specification would be enormously helpful documentation too. Because I've found it very difficult to figure out how exactly to do filtering.

Do you think you could already create a rough draft of this spec?

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Active » Closed (duplicate)
Related issues: +#2955020: Spec Compliance: JSON API's profile/extention (Fancy Filters, Drupal sorting, Drupal pagination, relationship arity) needs to be explicitly communicated

Closed this as a duplicate of #2955020: Spec Compliance: JSON API's profile/extention (Fancy Filters, Drupal sorting, Drupal pagination, relationship arity) needs to be explicitly communicated.