Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When a content type is renamed, entity references to that content type are still described in the schema using the original name.
For example, in the Contenta default install, "node--recipe" is renamed to "recipes". But the Article content type has a "recipes" entity reference that is described in the schema (viewed via /openapi/jsonapi) as:
"type": {
"type": "string",
"title": "Referenced resource",
"enum": [
"node--recipe"
]
}
I think "node--recipe" should be replaced in the above example with "recipes".
Comments
Comment #2
e0ipsoThis issue is probably a bug in the JSON API integration in the Schemata module. It is probably missing the translation to the internal name (
\Drupal::service('jsonapi.resource_type.repository')->get($entity_type_id, $bundle)->getPublicName($field_name)
).Comment #3
e0ipsoThis was fixed elsewhere.