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.
Updated: Comment 0
Problem/Motivation
Currently it is really exhausting to register a access checker as you have to create a service and specify the right tab.
Let's drop the need to specify a tag.
Before
views.route_access_check:
class: Drupal\views\ViewsAccessCheck
tags:
- { name: 'access_check' }
After
views.route_access_check:
class: Drupal\views\ViewsAccessCheck
Proposed resolution
Remaining tasks
User interface changes
API changes
Related Issues
Comment | File | Size | Author |
---|---|---|---|
#8 | access-2100131-8.patch | 11.3 KB | pwolanin |
#8 | 2100131-5-8.increment.txt | 1.11 KB | pwolanin |
#5 | access-2100131-3.patch | 11.06 KB | dawehner |
#3 | access-2100131-2.patch | 11.02 KB | dawehner |
#1 | access-2048223-70.patch | 79.63 KB | dawehner |
Comments
Comment #1
dawehnerHere is a simple try.
Comment #3
dawehnerThis was the wrong patch.
Comment #5
dawehnerThis was also wrong.
Comment #7
dawehnerFor some odd reasons the class are boolean at some point etc,
Comment #8
pwolanin CreditAttribution: pwolanin commentedI think it might work using is_subclass_of()
Comment #10
dawehnerSo this is blocked by #2100313: Move non-core services out of core.services.yml
Comment #11
dawehner... We don't do something similar somewhere else, so I don't think its worth to do. Maybe in 8.1.x we could introduce a general patterns
for all interface based services.
Note: Access checkers would need a specific tag anyway now, see the following example: