view release on metacpan or search on metacpan
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
view release on metacpan or search on metacpan
lib/App/Office/CMS.pm view on Meta::CPAN
$self -> log(debug => 'A message');
$self -> log(info => 'Another message');
=item o Validator.pm
This is used to validate CGI form data.
=back
=item o What's the database schema?
lib/App/Office/CMS.pm view on Meta::CPAN
=item o update()
=back
=item o App::Office::CMS::Util::Validator.validate_page()
=item o App::Office::CMS::Database::Page.save_page_record()
=item o App::Office::CMS::View::Page.build_update_page_html()
lib/App/Office/CMS.pm view on Meta::CPAN
templates. See below for details.
=item o Validator.pm
This is C<App::Office::CMS::Util::Validator>. You'll have to edit the
validate_design() method.
=item o The declaration of update_page_callback() (2 of 2)
This is in page.js. This is the Javascript function which receives the output
of CustomPage.pm.
view release on metacpan or search on metacpan
lib/App/Office/Contacts/Donations/Controller.pm view on Meta::CPAN
script_name => $self -> script_name,
session => $self -> param('session'),
tmpl_path => $self -> tmpl_path,
) );
if ($self -> validate_post == 0)
{
$self -> prerun_mode('Initialize');
}
} # End of cgiapp_prerun.
view release on metacpan or search on metacpan
lib/App/Office/Contacts/Import/vCards/Controller.pm view on Meta::CPAN
script_name => $self -> script_name,
session => $self -> param('session'),
tmpl_path => $self -> tmpl_path,
) );
if ($self -> validate_post == 0)
{
$self -> prerun_mode('Initialize');
}
} # End of cgiapp_prerun.
view release on metacpan or search on metacpan
lib/App/Office/Contacts.pm view on Meta::CPAN
Hence it will not be used by C<CGI> scripts, unless you write such a script yourself.
=item Validator.pm
This is used to validate CGI form data.
=back
=head2 Why did you use Sub::Exporter?
view release on metacpan or search on metacpan
lib/App/Oozie/Deploy.pm view on Meta::CPAN
if ( $verbose ) {
$logger->debug("Assert file: $absolute_path");
}
# assert_valid() does not display the error message, hence the manual check
my $error = $is_file->validate( $absolute_path ) || next;
$logger->logdie( sprintf 'required_tt_files(): %s', $error );
}
if ( $verbose ) {
$logger->debug( join q{=}, $_, $self->$_ ) for qw(
lib/App/Oozie/Deploy.pm view on Meta::CPAN
for my $xml_file ( $sv->local_xml_files ) {
my $parsed = $sv->maybe_parse_xml( $xml_file );
if ( my $error = $parsed->{error} ) {
$logger->fatal(
sprintf q{We can't validate %s since parsing failed: %s},
$parsed->{relative_file_name},
$error,
);
${ $validation_errors_ref }++;
${ $total_errors_ref }++;
lib/App/Oozie/Deploy.pm view on Meta::CPAN
\$validation_errors,
\$total_errors,
);
if ( $self->write_ownership_to_workflow_xml ) {
$self->validate_meta_file(
File::Spec->catfile( $workflow, $self->meta->file ),
\$validation_errors,
\$total_errors,
{},
);
lib/App/Oozie/Deploy.pm view on Meta::CPAN
}
return $validation_errors, $total_errors, $dest, $cvc;
}
sub validate_meta_file {
my $self = shift;
my $file = shift;
$self->logger->info( sprintf 'Extra validation for %s', $file );
lib/App/Oozie/Deploy.pm view on Meta::CPAN
=head2 run
=head2 upload_to_hdfs
=head2 validate_meta_file
=head2 verify_temp_dir
=head2 write_deployment_meta_file
view release on metacpan or search on metacpan
lib/App/OpenHAP/Devices.pm view on Meta::CPAN
# is called in a log line, which class builds it, and what that class
# needs beyond the fields every device has. Adding a type is one
# entry, and no second place to keep true.
#
# The class of the entry does the work of building. The loader only
# decides which one, validates the fields the configuration must
# carry, and subscribes the result to MQTT.
#
# A device class loads when the configuration asks for it, not at
# compile time. The classes drag JSON::XS and the whole accessory
# model behind them, and a tool that only reads the device blocks
lib/App/OpenHAP/Devices.pm view on Meta::CPAN
$dev_type, $dev_subtype );
return;
}
# Validate the required fields
return unless $self->_validate_device($device);
# Create the device and catch errors
my $accessory;
eval {
$accessory =
lib/App/OpenHAP/Devices.pm view on Meta::CPAN
}
return @devices;
}
# $self->_validate_device($device):
# Validate the required device fields. The method returns true
# if the device is valid.
sub _validate_device ( $self, $device )
{
unless ( defined $device->{name} && $device->{name} ne '' ) {
Fugu::Log->default->error(
'Device missing required field: name');
return;
view release on metacpan or search on metacpan
script/restart-opera view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
format (see --format)
log_level (see --log-level)
view release on metacpan or search on metacpan
lib/App/Options.pm view on Meta::CPAN
my ($type);
if ($option_defs) {
@vars = (sort keys %$option_defs);
foreach $var (@vars) {
$type = $option_defs->{$var}{type};
next if (!$type); # nothing to validate against
$value = $values->{$var};
next if (! defined $value);
if ($type eq "integer") {
if ($value !~ /^-?[0-9_]+$/) {
$exit_status = 1;
lib/App/Options.pm view on Meta::CPAN
=head2 Help and Validations
If the "-?" or "--help" options were set on the command line,
the usage statement is printed, and the program is exited.
Then each of the options which is defined may be validated.
If an option is designated as "required", its value must be
defined somewhere (although it may be the empty string).
(If it is also required to be a non-empty string, a regex
may be provided for the type, i.e. type => "/./".)