Skip Menu |

This queue is for tickets about the Catalyst-Runtime CPAN distribution.

Report information
The Basics
Id: 51676
Status: resolved
Priority: 0/
Queue: Catalyst-Runtime

People
Owner: jjnapiork [...] cpan.org
Requestors: ALTREUS [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 5.80013
Fixed in: (no value)



Subject: Debug table incorrect when newbies get chains wrong
Consider this setup package MyApp::Controller::Foo; sub args : Chained('/') {} sub moreargs : Chained('args') {} 1; Pretend that the actions had stuff in that showed us which one was hit, or something. The debug table looks like this: [debug] Loaded Chained actions: .-------------------------------------+--------------------------------------. | Path Spec | Private | +-------------------------------------+--------------------------------------+ | /args/... | /foo/args | | /args/moreargs/... | /foo/args | | | => /foo/moreargs | '-------------------------------------+--------------------------------------' Anyone familiar with chaining will know that this is wrong and why it is wrong but it is not caught. Obviously /args/moreargs can never be hit, so it should not show up. I guess this is mostly a problem for newbies who didn't realise that :Args(n) is a requirement, but a busy debug table would probably mask this mistake to oldbies as well.
We have a 'dangling chain links' report now, for several years. AFAIK this ticket have been solved a long time ago