Postponed (maintainer needs more info)
Project:
Drupal core
Version:
main
Component:
routing system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
18 Apr 2016 at 16:47 UTC
Updated:
26 Feb 2026 at 12:03 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #5
geek-merlinOK, so this largely was an IDE nobrainer, except for
* @var FQN namespaces,
* @inheritdoc
* removing unused import statements
(Any hints how to tweak PHPStorm settings to automate these?)
Patch flying in.
Setting major as this blocks stable contrib release of tim's initial work in #2621536: [admin_theme] Administration theme
Comment #6
tim.plunkettWait, me Tim? Did I work on that? I don't remember that, nor this being a hard blocker...
Comment #7
geek-merlinYeah, i often want to do stuff just to find i already did in my repo... Git says that's your code:
Well OK it may not be a hard blocker, just a kittenkiller...
Comment #8
borisson_Some nits. According to
$ ag AdminContextyou did replace all the instances.Oh, wow.
Does this work? I don't think we do this but I can't seem to find any documentation about it.
Should be only one newline
I don't think this comment is correct, this is the interface, not the class.
Needs a newline at the end of the file and a newline before the closing bracket of the class.
Should be the FQN.
Comment #9
geek-merlinThanks for the nits! I'll incorporate them.
5. FQN => MEMO to me, weed out how to make phpstorm do this by itself...
1. inheritdoc => in fact it's the rule:
https://www.drupal.org/docs/develop/coding-standards/api-documentation-a...
(other projects have the rule to leave this as it's just visual clutter and don't add info, but drupal decided for it, i guess api.drupal.org uses it)
Comment #10
borisson_#9, that documentation page talks about methods, not classes. I was talking about the class documentation there.
Comment #11
tim.plunkett{@inheritdoc} on a class makes no sense.
This bit should move back to the class, and the interface needs its own docblock explaining the generic concept of determining the admin-ness of a route.
The single implementation that we have is not a "helper class". It's one implementation of the interface that specifically checks for the route option of
_admin_route, and could explain that.Comment #12
geek-merlinAh yes i see. Here we go. New patch with nits 1-5.
Comment #14
geek-merlinLooks like a CI problem.
Comment #16
borisson_Nits were resolved. This looks good to go.
Comment #29
smustgrave commentedThank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #30
borisson_It still doesn't have an interface, so if we still want interfaces for all classes, I'm sure we can revive this. However I am not sure what the current policy is about that.
Comment #31
borisson_Discussed this a bit in slack with catch, we don't think this would ever need to be decorated or swapped out for another implementation.
https://drupal.slack.com/archives/C08HS1S71H7/p1772090051771109
I think we can close this issue.
Comment #32
borisson_At the very least, we can mark this as normal