Drupal Association members fund grants that make connections all over the world.
AccessibleInterface should have nothing to do with TypedData. That was a bizarre decision.
Similarly, AccessInterface is closely tied to routes, and has its own set of constants that are very helpful to understanding the difference between FALSE and NULL.
So let's please not add a 3rd system. Entity's usage of AccessibleInterface == the entity access controller...
From tim.plunkett in 1839516#95
Entity access just builds upon the typed data Accessibleinterface + have the controllers to implement it. It's not like it is a third system?
From fago in 1839516#96
AccessInterface is for routes. These are API hooks.
I know that it is for routes, though the interface is not part of the routing namespace, just saying ... and this might add some clarity
From Xano and dawehner in 2057377#25
The access check interfaces and classes are in the wrong place, which causes confusion about what they should be used for. Moving them to the routing namespace will prevent this, but the ternary constants should remain, so they can be used for other code as well.
- Future issues that will be able to convert boolean access control to use ternary return values in a well-documented way.
Issues that touch the same files
PASSED: [[SimpleTest]]: [MySQL] 59,040 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 59,056 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 59,276 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 58,784 pass(es). View
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch drupal_2095125_14.patch. Unable to apply patch. See the log in the details link for more information. View