Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Currently our entry point is a JSON API -ish response to the /jsonapi
endpoint. However, it could be worth adopting https://tools.ietf.org/html/draft-nottingham-json-home-06 for it and stop pretending that it's valid JSON API.
It's worth noting that moving to this new solution will break BC.
Proposed resolution
Discuss the value of this, given that we need to break BC to implement it.
Comments
Comment #2
Wim LeersOhhh!
This sounds very sensible :)
This also taught me about the existence of https://tools.ietf.org/html/rfc7240, which I'd never seen before.
Comment #3
dawehnerDo you believe people use that for their actual sites? At least for me this sounds like something you do during development time, which could be argued not any BC break.
Comment #4
dubcanada CreditAttribution: dubcanada commentedSo the proposal is to get rid of /jsonapi/ and respond to any requests containing the application/json-home Content-Type?
Comment #5
arifkhn46 CreditAttribution: arifkhn46 as a volunteer commentedIt think it should be configurable.
Comment #6
e0ipsoJSON API is zero configuration. I think it should remain so.
The plan is to replace only the entry point (/jsonapi). Every thing else remains the same.
Comment #7
e0ipsoComment #8
dawehnerI love this idea, ALSO because this makes it possible to not have this conversation in core and maybe keep jsonapi_extra in contrib land.
Comment #9
e0ipsoThis was done at some point.