The subtle changes of various internal call-chains in C<DBIC v0.0829xx> make
this silent uncertainty untenable. As a solution any such override will now
issue a descriptive warning that it has been bypassed during a
-C<< $rsrc->overriden_function >> invocation. A user B<must> determine how
+C<< $rsrc->overridden_function >> invocation. A user B<must> determine how
each individual override must behave in this situation, and tag it with one
of the above two attributes.
=head2 clone
- $rsrc_instance->clone( atribute_name => overriden_value );
+ $rsrc_instance->clone( atribute_name => overridden_value );
A wrapper around L</new> inheriting any defaults from the callee. This method
also not normally invoked directly by end users.
. "chain of calls within the convenience shortcut as seen when running:\n "
. '~$ perl -M%2$s -MDevel::Dwarn -e "Ddie { %3$s => %2$s->can(q(%3$s)) }"',
join (', ', map { "$_()" } sort @{ $_->{by} } ),
- $_->{overriden}{via_class},
- $_->{overriden}{name},
+ $_->{overridden}{via_class},
+ $_->{overridden}{name},
)} @{ $_[1] } ]
}
unless $_->{attributes}{DBIC_method_is_indirect_sugar};
push @err, {
- overriden => {
+ overridden => {
name => $_->{name},
via_class => (
# this way we report a much better Dwarn oneliner in the error