view release on metacpan or  search on metacpan

lib/App/Easer/V2.pod  view on Meta::CPAN

=item C<default_child>

   my $dc = $self->default_child;
   $self->default_child($new_name);

See L</Application High Level View>.

=item C<description>

   my $text = $self->description;
   $self->description($updated_description);

See L</Application High Level View>.

=item C<environment_prefix>

   my $prefix = $self->environment_prefix;
   $self->environment_prefix($new_prefix);

See L</Application High Level View>.

lib/App/Easer/V2.pod  view on Meta::CPAN

It is anyway possible to set callbacks or override the method at each
intermediate or at the leaf level, of course. In this case, the return
value of the method/callback will be used to determine whether to
continue up the ladder or not; I<true> values will continue the call
chain, I<false> values will interrupt it.

It's also possible to break the chain of calls by setting the key to a
I<false> value.

It MUST be considered that the method is specific to each command, which
usually does not have an I<updated> view of the whole configuration,
because that is only known to the leaf command's object. For this
reason, method/callback C<final_commit> can also call method
C<final_commit_stack>, which provides a list of all command objects that
are involved in the chain, starting from the leaf command down towards
the root.

For this reason, the way to get the I<full> configuration in the topmost
command is the following:

   sub final_commit ($self) {