The core entity reference field does not document any requirement that the main property name on the field is the same as the value of the entity ID.
However, the code in jsonapi module assumes this is true in at least a couple places. This breaks subclasses of EntityReferenceItem that use the UUID (e.g. entity_reference_uuid module) or some other unique identifier (e.g. the revision ID) as the main property.
related:
#3050845: Includes using the `entity_reference_uuid` contrib module not working →
🐛
Cannot use UUID as entity ID
Needs work
Using the entity_reference_uuid module, try to include related data for the reference filed, or try to send a PATCH request to the relationship URL
Since we are already loading the entity, we can simply use/assign the "entity" property on the reference field instead of trying to guess the mapping of entity ID to property name.
port contrib patch, update core patch
n/a
n/a
n/a
todo
Active
11.0 🔥
jsonapi.module
Ok, moved it to an issuefork so we can get tests.
Although this seems fine, we do need some testing around this. I guess testing the 2 changed methods might be good enough, but not entirely sure yet how to do that.