Problem/Motivation

REST clients can GET an entity resource, which includes values for fields that the user is allowed to view. However, the REST client then does not know which of these fields the user is allowed to edit.

Proposed resolution

  • For the HAL format, we're already returning 'type' link relations with the entity resource. The URI of that is defined in TypeLinkManager::getTypeUri(), the current documentation of which explains that this is a URI without a core-provided resource backing it. So one possible solution to this issue is to implement that resource.
  • If we do #2664876: Add JsonApi (application/vnd.api+json) and deprecate HAL?, then JsonAPI provides its own specification for inlining metadata into the entity resource.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

effulgentsia created an issue. See original summary.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.