On 6 Feb 2007, at 18:37, John Napiorkowski wrote:
So should we consider reflect_actions_for to be
deprecated? Because right now if your DBIC classes
are anywhere other than in a folder right underneath
the Schema the trunk version won't work.
Hmm? Just pass it __PACKAGE.'::Prefix' instead of
On Feb 5, 2007, at 5:58 PM, John Napiorkowski wrote:
Hi,
Is there a test suite for Reaction other than the
sample application at the source control site?
Because I have a patch to fix a problem with the DBIC
action reflector not properly creating actions for
DBIC classes in a deep hierarchy
On 6 Feb 2007, at 15:33, John Napiorkowski wrote:
--- Jason Kohles [EMAIL PROTECTED] wrote:
On Feb 5, 2007, at 5:58 PM, John Napiorkowski wrote:
Hi,
Is there a test suite for Reaction other than the
sample application at the source control site?
Because I have a patch to fix a problem
On 6 Feb 2007, at 16:15, John Napiorkowski wrote:
package manage::Model::Action;
my $r = ActionReflector-new;
$r-reflect_action_for(
'mylib::schemas::db::membership::members',
__PACKAGE__.'membership::members::create',
'Create',
);
[one of the above for each action type]
Would also
--- Matt S Trout [EMAIL PROTECTED] wrote:
On 6 Feb 2007, at 16:15, John Napiorkowski wrote:
package manage::Model::Action;
my $r = ActionReflector-new;
$r-reflect_action_for(
'mylib::schemas::db::membership::members',
__PACKAGE__.'membership::members::create',
Hi,
Is there a test suite for Reaction other than the
sample application at the source control site?
Because I have a patch to fix a problem with the DBIC
action reflector not properly creating actions for
DBIC classes in a deep hierarchy (like
myschema::membership::members) but since I could
