Routes with default values for "multiple route part" segments are not resolved correctly
|Priority:||Must have||Due date:|
|Assignee:||Bastian Waidelich||% Done:||
|Has patch:||FLOW3 version affected:|
With the new possibility to add multiple route parts in one URL pattern segment (see #1250) a new issue emerged:
The route "[firstName]-[lastName]/[@action]" is not resolved correctly if defaults are set for lastName and @action and lastName is empty in request URL (e.g. "john-/list").
This happens because static route part handler cuts first url segment from request path when matching the hyphen.
- FLOW3: (MVC) Added new property "lastRoutePartInSegment" to F3_FLOW3_MVC_Web_Routing_StaticRoutePart to indicate whether a route part is the last in the current url segment. This fixes #1264.
Routing classes are quite messy and complex at the moment. Refactoring and cleanup is needed!