No subject


Thu Feb 23 00:47:41 CET 2006


the attribute to Chained() - it seemed the method name didn't really
matter (it just happened to be the default PathPart name if you didn't
specify it). However, in practice, that's not how's it working.

Some weird stuff also happens if you specify PathPart actions as such:

  sub another_test  : PathPart Chained('/') {}
  sub another_test2 : PathPart Chained('another_test') {}

It will result in:

[debug] Loaded Path Part actions:
.-------------------------------------+--------------------------------------.
| Path Spec                           | Private                              |
+-------------------------------------+--------------------------------------+
| /another_test/...                   | /login/another_test                  |
| /another_test/another_test2/...     | /login/another_test                  |
|                                     | => /login/another_test2              |
'-------------------------------------+--------------------------------------'

But /another_test/another_test2/ isn't actually callable. But this
latter one is probably an abuse of the chained actions system. ;-)

The first issue, however, still seems to exhibit a somewhat weird
behaviour to me, so I'd welcome at least a little bit of enlightenment
on the matter (ie. if that's really the expected behaviour, what's the
rationale behind it).

Anyway, I'm really enjoying all these new features. Hope you guys keep
up the nice work. ;-)

-Nilson Santos F. Jr.



More information about the Catalyst mailing list