AccessibleInterface is part of typed data, but it does not require typed data in any way. However, in its current form it is usable for *any* object that is accessible and wants to control access to itself. Let's move it from \Drupal\TypedData to \Drupal\Access

AccessibleInterface should have nothing to do with TypedData. That was a bizarre decision.

tim.plunkett in 1839516#95.

CommentFileSizeAuthor
#4 drupal_2095233_4.patch5.95 KBXano
#1 drupal_2095233_1.patch4.88 KBXano
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Xano’s picture

Xano
he/they
Primary language English
Location Southampton
CreditAttribution: Xano commented
Assigned: Xano » Unassigned
Status: Active » Needs review
FileSize
drupal_2095233_1.patch4.88 KB
Xano’s picture

Xano
he/they
Primary language English
Location Southampton
CreditAttribution: Xano commented
Issue tags: +DX (Developer Experience)

Status: Needs review » Needs work

The last submitted patch, drupal_2095233_1.patch, failed testing.

Xano’s picture

Xano
he/they
Primary language English
Location Southampton
CreditAttribution: Xano commented
Status: Needs work » Needs review
FileSize
drupal_2095233_4.patch5.95 KB

If #2095125: Use access constants in every access control context gets in, we can make AccessibleInterface implement \Drupal\Core\Access\AccessInterface and AccessibleInterface::access() can return those constants rather than simple booleans.

Xano’s picture

Xano
he/they
Primary language English
Location Southampton
CreditAttribution: Xano commented
Status: Needs review » Closed (duplicate)

As per my discussion with tim.plunkett, this will be done in #2095125: Use access constants in every access control context.