Add support for jsonapi_extras & jsonapi_defaults

Created on 1 June 2018, over 6 years ago
Updated 20 November 2023, 12 months ago

It would be nice to make sure this fully supports/works with JSON API Extras (specifically, the configurable path prefix) and JSON API Defaults .

Feature request
Status

Needs work

Version

2.0

Component

Code

Created by

🇩🇪Germany jan.stoeckler

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇫🇷France sashainparis Provins

    JsonAPI Defaults is made to define default queries to JsonAPI: IMHO, it applies to collections.

    Path alias hardly apply to collections of entities. So I'm not sure to link JsonAPI Aliases module to JsonAP Defaults.

    JsonAPI Extras define its configuration to a dedicated page under the JsonAPI configuration page.

    A dedicated configuration page should has its own tab under JsonAPI configuration page too: Mainly to define the endpoint.

    At Resource level in JsonAPI Extras, one can consider to add a Aliases fieldgroup (after Resource, and before the fields): to enable/disable the resource.

  • 🇫🇷France sashainparis Provins

    JsonAPI Extras compatibility solved in 2.0.0-Alpha5: To use the path-prefix defined there.

Production build 0.71.5 2024