Closed (fixed)
Project:
JSON:API Extras
Version:
8.x-3.x-dev
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
12 Mar 2019 at 22:52 UTC
Updated:
11 Apr 2019 at 09:29 UTC
Jump to comment: Most recent, Most recent file



Comments
Comment #2
e0ipso@Wim Leers now that JSON:API 2.4 has been released, is this actionable?
Comment #3
e0ipsoComment #4
e0ipsoComment #5
wim leersYes!
Comment #6
wim leersComment #7
e0ipsoScreenshots look good. I'll check the code later.
Comment #8
wim leersNow that #3035134: Compatibility with upcoming JSON:API 2.4 release: JSON:API Extras 3.5 landed, we should be able to do this easily.
Comment #9
e0ipsoCode looks good. There are some opinionated changes in terminology and paths that I'm neutral about.
I'll kick a test for version of core that already contains JSON:API.
Comment #10
wim leersIf they're at all contentious, I'll just change it. But per https://jsonapi.org/format/, isn't it "resource types" that you're tweaking using JSON:API Extras? You're never tweaking a
node--articleresource, you're tweaking thenode--articleresource type, and hence tweaking allnode--articleresources?If you have reservations about this, I'm happy to revert those changes. I changed it because it thoroughly confused me.
Comment #11
e0ipsoI'm wondering if this makes JSON:API Extras not compatible with the core version because they both declare the same route.
Ideally we'd want to have a single JSON:API Extras version that works for D8.6 + JSON:API contrib + JSON:API Extras and D8.7 + JSON:API Extras.
Any ideas?
Comment #12
e0ipsoI also opened #3043975: Unable to install JSON:API Extras with core JSON:API using composer to try and capture those combinations while running tests in the Drupal CI.
Comment #13
e0ipsoI dropped a duplicate menu. I also made some minor language changes.
Comment #14
e0ipsoComment #16
e0ipsoMerged! Time for a release.
Comment #17
wim leers#11: JSON:API 2.4 is identical to what's in core. So 8.6 or 8.5 + JSON:API 2.4 and Drupal 8.7 or 8.8 behave exactly the same for JSON:API Extras. So I don't get what you mean by "not compatible with the core version"?
#13: dropping the menu: nice one! Looks like you disagreed with #10, but that's okay — that was kind of out of scope anyway. I'm still confused by this, but I won't insist on it obviously :)