Whilst the 'nominate individual methods as dispatchable by their metaclass' strategy...
authort0m <bobtfish@bobtfish.net>
Mon, 25 May 2009 16:26:43 +0000 (17:26 +0100)
committert0m <bobtfish@bobtfish.net>
Mon, 25 May 2009 16:26:43 +0000 (17:26 +0100)
commit03788421e34f1a526041fdc8c7b3ade00b0535cd
tree836c140993e330ff1944193428131de96ba36f84
parentf5cb8a519704a0541817a4700aadad1a11b49ff8
Whilst the 'nominate individual methods as dispatchable by their metaclass' strategy is reasonable, we actually want to be able to make the strategies pluggable, and encourage 'class consumes an interface role' as the default way of doing it. Therefore, as I have no intention of documenting it, or really maintaining it to be more useable than as a test case for an alternate method finding implementation, then I'm moving the relevant code to generate those methods down into the tests
t/lib/ControllerGeneratingModel.pm [moved from lib/CatalystX/ControllerGeneratingModel.pm with 100% similarity]
t/lib/ControllerGeneratingModel/DispatchableMethod.pm [moved from lib/CatalystX/ControllerGeneratingModel/DispatchableMethod.pm with 100% similarity]