Problem/Motivation
CurrentRouteMatch::getRouteMatch() is smart enough to only statically cache the route match once it believe routing has finished.
Unfortunately, a complex RouteFilter (like the one in Page Manager) may need to alter the request during filtering, and if any code calls the route match during that process, a stale request will be stored.
Proposed resolution
Add a method to reset the route match static cache.
Remaining tasks
N/A
User interface changes
N/A
API changes
BC-compatible API addition: A new CurrentRouteMatchInterface is used and is given the new resetRouteMatch() method.
Data model changes
N/A