Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

html::formhandler::manual::fromdfv(3pm) [debian man page]

HTML::FormHandler::Manual::FromDFV(3pm) 		User Contributed Perl Documentation		   HTML::FormHandler::Manual::FromDFV(3pm)

NAME

       HTML::FormHandler::Manual::FromDFV - converting from Data::FormValidator

VERSION

       version 0.40013

SYNOPSIS

       Manual Index

       Cheatsheet for converting from Data::FormValidator.

DESCRIPTION

       Information that's useful when switching from Data::FormValidator to HTML::FormHandler. There's not a lot here yet, so if you have
       something to add, patches are welcome.

       In a general way, FormHandler doesn't have nearly so many "special" checks as Data::FormValidator. It would be possible to implement many
       of them, but there hasn't been much demand for them. So far FormHandler users seem to be satisfed with the "do your own checks in a Perl
       method" solution. Because of the greater complexity of FormHandler's data model - with Repeatable arrays and nested compounds, etc - it's
       somewhat harder to do some of them automatically.

Differences/conversions
       dependencies
	   In FormHandler, 'dependency' is the equivalent of 'dependency_group', without the key names.

	   The other variations of dependencies in DFV are not implemented in FormHandler, and would normally be done in a form's 'validate' sub.

       trim, filters
	   A 'trim' filter is installed by default in FormHandler; it's a special version of an apply action, and can be set to a transform or
	   Moose type. See the documentation in HTML::FormHandler::Field#trim.

	   Transforms and inflations/deflations do not change what is presented in the form unless you set the 'fif_from_value' flag on the field.

       FV_length_between, FV_max_length, FV_min_length
	   Use text fields with 'minlength' and 'maxlength' attributes.

       FV_eq_with
	   Perform your own checks in the form 'validate' sub.

	       sub validate {
		   my $self = shift;
		   if( $self->field('one')->value eq $self->field('two')->value ) {
		   }
	       }

Constraints
       The simple constraints from Data::FormValidator::Constraints can be used directly in a FormHandler form:

	   use Data::FormValidator::Constraints ('match_state');
	   has_field 'my_state' => (
	       apply => [ { check => &match_state, message => 'Invalid State' } ] );

       email
	   Use the 'Email' field type, or use the the FH Moose Type, 'email'.

		has_field 'email' => ( type => 'Email' );
		-- or --
		use HTML::FormHandler::Types ('Email');
		has_field 'email' => ( apply => [ Email ] );

AUTHOR

       FormHandler Contributors - see HTML::FormHandler

COPYRIGHT AND LICENSE

       This software is copyright (c) 2012 by Gerda Shank.

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.14.2							    2012-06-25				   HTML::FormHandler::Manual::FromDFV(3pm)

Check Out this Related Man Page

HTML::FormHandler::TraitFor::I18N(3pm)			User Contributed Perl Documentation		    HTML::FormHandler::TraitFor::I18N(3pm)

NAME

       HTML::FormHandler::TraitFor::I18N - localization

VERSION

       version 0.40013

       language_handle, _build_language_handle

       Holds a Locale::Maketext (or other duck_type class with a 'maketext' method) language handle. The language handle is used to localize the
       error messages in the field's 'add_error' method. It's also used in various places in rendering to localize labels and button values, etc.

       The builder for this attribute gets the Locale::Maketext language handle from the environment variable $ENV{LANGUAGE_HANDLE}:

	   $ENV{LANGUAGE_HANDLE} = HTML::FormHandler::I18N->get_handle('en_en');

       ...or creates a default language handler using HTML::FormHandler::I18N.	You can pass in an existing Locale::MakeText subclass instance or
       create one in a builder.

       In a form class:

	   sub _build_language_handle { MyApp::I18N::abc_de->new }

       Passed into new or process:

	   my $lh = MyApp::I18N::abc_de->new;
	   my $form = MyApp::Form->new( language_handle => $lh );

       If you do not set the language_handle, then Locale::Maketext and/or I18N::LangTags may guess, with unexpected results.

       You can use non-Locale::Maketext language handles, such as Data::Localize.  There's an example of building a Data::Localize language handle
       in t/xt/locale_data_localize.t in the distribution.

       If you don't want a particular error message to go through localization, you can use 'push_errors' and 'push_form_errors' instead of
       'add_error' and 'add_form_errors'.

       Example of getting the language handle from the Catalyst context (where the Catalyst context is passed in with 'ctx'):

	   has '+language_handle' => ( builder => 'get_language_handle_from_ctx' );
	   sub get_language_handle_from_ctx {
	       my $self = shift;
	       return MyApp::I18N->get_handle(
		   @{ $self->ctx->languages } );
	   }

AUTHOR

       FormHandler Contributors - see HTML::FormHandler

COPYRIGHT AND LICENSE

       This software is copyright (c) 2012 by Gerda Shank.

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.14.2							    2012-06-25				    HTML::FormHandler::TraitFor::I18N(3pm)
Man Page