Closed (fixed)
Project:
JSON:API
Version:
8.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
2 Jan 2018 at 11:30 UTC
Updated:
17 Jan 2018 at 12:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
gabesulliceThis also adds some comments and fixes some code standard violations.
Comment #3
e0ipsoI'm good with this in spirit. However I'm starting to worry about churn generated by personal preferences and code style idiosyncrasies.
To make myself clear: I think this patch is an improvement and we should commit it.
On a separate note, we should try to not increase patch size only to please our personal taste (array_reduce vs foreach, 0 cyclomatic complexity vs low cyclomatic complexity, type hinting vs comment based typed hinting, different wording in comments, …) unless it's justified (the previous comment wording misleading, we need side-effects in the loop, …).
I'll do a review of the patch soon.
Comment #4
wim leersMaking the code easier to understand for more people is worthwhile, right? I agree if it's pure coding style changes (except if it's making the code conform to core's coding standards, that's always okay). But in this case
Patch review:
These
\nadditions are pure personal preference. Let's revert these.This is the bugfix. Let's not fix bugs here, let's *only* clean up existing code.
We should convert this to a
@dataProvider. That'd make it even clearer.Comment #5
e0ipso+10
+1
I agree this case is mostly that, I wanted to clarify that upfront with:
Comment #6
wim leersYep, I figured, but I just wanted to check some of the nuances with you :) Glad to see we're once again on the same page!
Comment #7
gabesulliceDone.
Comment #8
wim leersThis method is still being added, but no longer being used. Should be removed.
Once that's fixed, this is RTBC IMHO.
Comment #9
gabesulliceComment #10
wim leersComment #11
e0ipso👏🏽🚢
Comment #13
e0ipsoComment #14
wim leers#11: :D
Now #2920194: Inclusion of nested relationships fails for bundle-specific fields can continue!