Drupal Association members fund grants that make connections all over the world.
This is a follow-up to(this might be a potential novice issue or something for future core office hours)
The are some methods of EntityTranslationControllerInterface which should be best located elsewhere:
The getAccess() method should be removed as soon as we have entity access available: ,
Use a more generic solution.
Kind of postponed on (the changes will be made to the code that that introduces)
Once those land, post a patch to remove getAccess()
Then, do reviews, update or write tests, evaluate if documentation or a change notice is needed.
User interface changes
Most likely, *no* new or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text.
This will probably be a small internal change and no major API changes/additions that would affect module, install profile, and theme developers. We could include an example of before/after code.
The getAccess() method should be removed as soon as we have entity access available and replaced with EnttyInterface::access() calls or something along those lines.
And responded in support of making this a follow-up in
This sounds like it would be a followup to this patch once/if entity access lands. I'm not seeing an outpouring of activity on, so looks like this is likely a no-go for Drupal 8 anyway, and nodes will stay special.
PASSED: [[SimpleTest]]: [MySQL] 58,001 pass(es). View
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch core-remove_getaccess-1810320-8.patch. Unable to apply patch. See the log in the details link for more information. View