Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

catalyst::action::renderview(3pm) [debian man page]

Catalyst::Action::RenderView(3pm)			User Contributed Perl Documentation			 Catalyst::Action::RenderView(3pm)

NAME
Catalyst::Action::RenderView - Sensible default end action. SYNOPSIS
sub end : ActionClass('RenderView') {} DESCRIPTION
This action implements a sensible default end action, which will forward to the first available view, unless "$c->res->status" is a 3xx code (redirection, not modified, etc.), 204 (no content), or "$c->res->body" has already been set. It also allows you to pass "dump_info=1" to the url in order to force a debug screen, while in debug mode. If you have more than one view, you can specify which one to use with the "default_view" config setting and the "current_view" and "current_view_instance" stash keys (see Catalyst's "$c->view($name)" method -- this module simply calls "$c->view" with no argument). METHODS
end The default "end" action. You can override this as required in your application class; normal inheritance applies. INTERNAL METHODS
execute Dispatches control to superclasses, then forwards to the default View. See "METHODS/action" in Catalyst::Action. SCRUBBING OUTPUT
When you force debug with dump_info=1, RenderView is capable of removing classes from the objects in your stash. By default it will replace any DBIx::Class resultsource objects with the class name, which cleans up the debug output considerably, but you can change what gets scrubbed by setting a list of classes in $c->config->{'Action::RenderView'}->{ignore_classes}. For instance: $c->config->{'Action::RenderView'}->{ignore_classes} = []; To disable the functionality. You can also set config->{'Action::RenderView'}->{scrubber_func} to change what it does with the classes. For instance, this will undef it instead of putting in the class name: $c->config->{'Action::RenderView'}->{scrubber_func} = sub { undef $_ }; Deprecation notice This plugin used to be configured by setting "$c->config->{debug}". That configuration key is still supported in this release, but is deprecated, please use the 'Action::RenderView' namespace as shown above for configuration in new code. EXTENDING
To add something to an "end" action that is called before rendering, simply place it in the "end" method: sub end : ActionClass('RenderView') { my ( $self, $c ) = @_; # do stuff here; the RenderView action is called afterwards } To add things to an "end" action that are called after rendering, you can set it up like this: sub render : ActionClass('RenderView') { } sub end : Private { my ( $self, $c ) = @_; $c->forward('render'); # do stuff here } AUTHORS
Marcus Ramberg <marcus@thefeed.no> Florian Ragwitz <rafl@debian.org> COPYRIGHT
Copyright (c) 2006 - 2009 the Catalyst::Action::RenderView "AUTHOR" as listed above. LICENSE
This library is free software. You can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2011-01-05 Catalyst::Action::RenderView(3pm)

Check Out this Related Man Page

Jifty::Action::Record::Update(3pm)			User Contributed Perl Documentation			Jifty::Action::Record::Update(3pm)

NAME
Jifty::Action::Record::Update - Automagic update action DESCRIPTION
This class is used as the base class for Jifty::Actions that are merely updating Jifty::Record objects. To use it, subclass it and override the "record_class" method to return the name of the Jifty::Record subclass that this action should update. METHODS
arguments Overrides the "arguments" in Jifty::Action::Record method to further specify that all of the primary keys must have values when submitted; that is, they are constructors. validate_arguments We only need to validate arguments that got submitted -- thus, a mandatory argument that isn't submitted isn't invalid, as it's not going to change the record. This is opposed to the behavior inherited from Jifty::Action, where mandatory arguments must be present for the action to run. However, constructor arguments are still required. take_action Overrides the virtual "take_action" method on Jifty::Action to call the appropriate "Jifty::Record"'s "set_" methods when the action is run, thus updating the object in the database. report_success Sets the "message" in Jifty::Result to default success message, "Updated". Override this if you want to report some other more user- friendly result. possible_columns Update actions do not provide fields for columns marked as "private" or "protected". _extra_validator_args Passes "for => 'update'" to validators. _extra_canonicalizer_args Passes "for => 'update'" to canonicalizers. _extra_autocompleter_args Passes "for => 'update'" to autocompleters. SEE ALSO
Jifty::Action::Record, Jifty::Record LICENSE
Jifty is Copyright 2005-2010 Best Practical Solutions, LLC. Jifty is distributed under the same terms as Perl itself. perl v5.14.2 2011-02-10 Jifty::Action::Record::Update(3pm)
Man Page