Closed (fixed)
Project:
JSON:API
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
11 Jan 2017 at 10:35 UTC
Updated:
27 Jan 2017 at 13:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
wim leersAnd patch.
This is relative to #2842378: Remove all remaining interfaces in the JSON API module that have only one implementation, so postponing on that.
Comment #3
wim leersOops, I forgot to add the final bits of work.
Comment #4
e0ipsoComment #5
wim leersYay, green :)
Comment #6
hampercm commentedReviewing...
Comment #7
hampercm commentedLooks good!
Comment #8
e0ipsoI think that the normalizers should not be internal. This is the main tool implementors can use to add their custom properties and alter the input/output of the API (by creating normalizers that extend from ours).
Thoughts?
Comment #9
e0ipsoThis is what I was proposing in #8.
Comment #10
wim leersI think that's okay for now, as long as JSON API would be alpha-experimental in Drupal core, because everything is allowed to change anyway.
But marking everything
@internalis purely a preventative measure: it means we explicitly signal everything can still change. Not marking something@internalmeans you're free to extend from it for your own needs, and then if we change the logic of, say, the Field or ContentEntity normalizer, that could then break this custom normalizer. Which means we must FOREVER keep the normalizers work exactly the same. That is what I'm protecting against.Of course, contrib/custom modules are free to add their own normalizers. I just want to make sure they don't depend on JSON API's normalizers.
Comment #11
e0ipsoRe-rolled and merged.
Comment #12
e0ipso