Task #3441
Routing: Don't process routes in reverse order
| Status: | Resolved | Start date: | 2009-05-24 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Bastian Waidelich | % Done: | 100% |
|
| Category: | MVC | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 1 | |||
| Sprint: | Has patch: | |||
| PHP Version: | Complexity: |
Description
Currently routes are processed from bottom to top.
We decided to change that as it seems to be more intuitive to work off routes from top to bottom.
It should be enough to remove the array_reverse calls in \F3\FLOW3\Web\Routing\Router.
Related issues
Associated revisions
FLOW3:
- !!! BREAKING CHANGE !!! F3\FLOW3\Configuration\Manager is now able to load sub routes from packages and merge them with main routes. Resolves #2126 (This needs further testing and some cleanup!)
- !!! BREAKING CHANGE !!! Routes are not processed in reverse order anymore. Resolves #3441.
- Query string won't be lowercased anymore by the routing framework. Relates to #2237.
- Added some missing type hints to F3\FLOW3\Configuration\Manager
- Improved exception messages in F3\FLOW3\MVC\Web\Routing\Route
FLOW3 Distribution: - !!! BREAKING CHANGE !!! adapted global routes to the changes mentioned above and added subroutes to FLOW3/TYPO3CR packages.
FLOW3:
- !!! BREAKING CHANGE !!! F3\FLOW3\Configuration\Manager is now able to load sub routes from packages and merge them with main routes. Resolves #2126 (This needs further testing and some cleanup!)
- !!! BREAKING CHANGE !!! Routes are not processed in reverse order anymore. Resolves #3441.
- Query string won't be lowercased anymore by the routing framework. Relates to #2237.
- Added some missing type hints to F3\FLOW3\Configuration\Manager
- Improved exception messages in F3\FLOW3\MVC\Web\Routing\Route
FLOW3 Distribution: - !!! BREAKING CHANGE !!! adapted global routes to the changes mentioned above and added subroutes to FLOW3/TYPO3CR packages.
History
#1 Updated by Robert Lemke about 6 years ago
ack
#2 Updated by Karsten Dambekalns about 6 years ago
Go ahead!
#3 Updated by Bastian Waidelich about 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r2381.