Closed (fixed)
Project:
JSON:API
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
29 Aug 2018 at 20:08 UTC
Updated:
24 Sep 2018 at 16:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
wim leersThis is what you mean, right?
Comment #3
wim leersPerhaps something like this?
Comment #5
gabesulliceYep, that's exactly it.
I started with the tests though and did some clean up that preps #2956084: Impossible to raise an error when an `include` is requested for an inaccessible relationship field..
Test only patch + cleanup is the interdiff.
Comment #7
gabesulliceComment #9
gabesulliceRerolled.
Comment #11
gabesulliceAh, nice catch! /me high-fives the testbot.
That error reminded me of something that bothered me before...
In #3, link keys lost their non-deterministic property, i.e. the same URLs always have the same hash. That means it would theoretically be possible to hardcode a client to look for that hash. It was necessary to do that in order to deduplicate items by their URL, but it's not necessary for that to be true across requests.
I don't want clients to even have the possibility to hardcode a link key hash. So this interdiff introduces a salt in order to get the best of both worlds :)
Comment #13
gabesulliceWhoops, that was a silly oversight.
Comment #14
wim leersComment #16
gabesullice