Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
routing system
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
27 Jun 2014 at 20:12 UTC
Updated:
19 Jan 2015 at 13:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tim.plunkettComment #3
tim.plunkettForgot to adjust core.services.yml for action manager.
Comment #4
tim.plunkettThese are the *actual usages* of Request that are now RouteMatch.
Comment #5
xjmComment #6
tim.plunkettComment #7
dawehnerDid we actually ever considered to move the routeMatch interface into Drupal/Component? This could be really useful for other code as well and allows people to write generic libraries without pulling in all of drupal.
It is a bit odd that we need both the request and the route match object. It could be possible to construct another request object based upon a routeMatch, which indeed could be really convenient, because the route match just contains high-level results.
Comment #8
effulgentsia commentedRe #7.1: good idea: #2296205: Create a \Drupal\Component\Routing\ namespace and move Drupal-independent routing classes into it.
Re #7.2: yeah, that seems wrong. We should make getRouteParameters() and getOptions() have the same signature, so needs work on that. Also, in #2292217: ThemeNegotiator::determineActiveTheme() should not require a RouteMatch to be passed in, the RTBC patch there switched to removing $route_match from a passed-in parameter to a CI dependency. Should we consider the same approach here?
Comment #9
dawehner@effulgentsia
Well, I made a comment on that issue that I think it not in doens't make sense.
Also here, if you provide custom plugins you most often will do things dynamically, so it seems wrong
that you have to pass it along via CI.
Personally my mind modell is the same as the account on the various access(AccountInterface $accountb) methods.
Comment #10
tim.plunkettDidn't switch to CI, because that's still under debate in the other issue.
Fixed getRouteParameters().
Comment #11
dawehnerI like it just like it is. So how do we resolve the two situations?
Comment #12
tim.plunkettI would consider both of these improvements.
Comment #15
tim.plunkettComment #16
dawehnerRerolled the approach with the passed route match object.
Comment #18
dawehnerThat was probably easy.
Comment #19
catchThis is now blocking #2281619: Convert most direct usages within module code of routing related request attributes to use RouteMatchInterface instead so bumping.
Comment #20
jibranIt's ready.
Comment #21
catchLooks great. We can nearly remove the request stack from
\Drupal\Core\Menu\LocalActionManagerbut still one usage there.Committed/pushed to 8.0.x, thanks!