#764: Allow nested routing structures with concatenated name or action
attributes
in ancestors other than immediate parents
-------------------------+--------------------------------------------------
Reporter: david | Owner: dominik
Type: enhancement | Status: new
Priority: low | Milestone: 0.11.2
Component: routing | Version: 0.11.1
Severity: minor | Keywords:
Has_patch: 0 |
-------------------------+--------------------------------------------------
{{{
<route name="foo" pattern="^/foo" module="Default" action="Foo">
<route pattern="^/dummy">
<route name=".bar" pattern="^/bar" action=".Bar" />
}}}
Then, {{{foo.bar}}} will generate {{{/foo/dummy/bar}}}, and a match will
run action {{{Foo.Bar}}} (right now, it looks only at the immediate parent
to resolve the full name of {{{.bar}}} and action {{{.Bar}}})
Patterns, however, still cannot be "skipped" this way.
--
Ticket URL: <http://trac.agavi.org/ticket/764>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
