SignatureTemplate($c, Forms::RequestEmailVerification)

[jjn1056]

just a placeholder before I forget

[jjn1056]

There's a action role for this, but I'd love to see this more built into the action to encourage experimentation a bit

https://metacpan.org/pod/Catalyst::ActionRole::MethodSignatureDependencyInjection

[jjn1056]

thoughts

First we'd have an interface in Catalyst::Action for describing the signature. Things to figure would be stuff like the bits that get checked in match/match captures(args). This signature would probably be an array of hash-refs (or possible an array of objects). There might be an overall container object for the signature as well.

Second, we'd like an Actionrole that would let you set the signature via a DSL mini language using an attribute (sub attribute or via the config

: Does(Signature) Signature($sig)

Where $sig would be something we can parse and use to populate the signature API.

Questions

How should we resolve when the signature declares Args / Captures? Should we use that information to popular Args / CaptureArgs in the case when those don't independently exist? My guess at this point is we should keep them separate.