NAME

Perinci::Examples::Tiny::Args - Tests related to function arguments

VERSION

This document describes version 0.824 of Perinci::Examples::Tiny::Args (from Perl distribution Perinci-Examples), released on 2023-07-09.

DESCRIPTION

Like the other Perinci::Examples::Tiny::*, this module does not use other modules and is suitable for testing Perinci::CmdLine::Inline as well as other Perinci::CmdLine frameworks.

FUNCTIONS

as_is

Usage:

as_is(%args) -> [$status_code, $reason, $payload, \%result_meta]

This function returns the argument as-is.

This function is not exported.

Arguments ('*' denotes required arguments):

  • arg => any

    (No description)

Returns an enveloped result (an array).

First element ($status_code) is an integer containing HTTP-like status code (200 means OK, 4xx caller error, 5xx function error). Second element ($reason) is a string containing error message, or something like "OK" if status is 200. Third element ($payload) is the actual result, but usually not present when enveloped result is an error response ($status_code is not 2xx). Fourth element (%result_meta) is called result metadata and is optional, a hash that contains extra information, much like how HTTP response headers provide additional metadata.

Return value: (any)

has_date_and_duration_args

Usage:

has_date_and_duration_args(%args) -> [$status_code, $reason, $payload, \%result_meta]

This function contains a date and a duration argument.

This function is not exported.

Arguments ('*' denotes required arguments):

  • date* => date

    (No description)

  • duration* => duration

    (No description)

Returns an enveloped result (an array).

First element ($status_code) is an integer containing HTTP-like status code (200 means OK, 4xx caller error, 5xx function error). Second element ($reason) is a string containing error message, or something like "OK" if status is 200. Third element ($payload) is the actual result, but usually not present when enveloped result is an error response ($status_code is not 2xx). Fourth element (%result_meta) is called result metadata and is optional, a hash that contains extra information, much like how HTTP response headers provide additional metadata.

Return value: (any)

has_date_arg

Usage:

has_date_arg(%args) -> [$status_code, $reason, $payload, \%result_meta]

This function contains a date argument.

This function is not exported.

Arguments ('*' denotes required arguments):

  • date* => date

    (No description)

Returns an enveloped result (an array).

First element ($status_code) is an integer containing HTTP-like status code (200 means OK, 4xx caller error, 5xx function error). Second element ($reason) is a string containing error message, or something like "OK" if status is 200. Third element ($payload) is the actual result, but usually not present when enveloped result is an error response ($status_code is not 2xx). Fourth element (%result_meta) is called result metadata and is optional, a hash that contains extra information, much like how HTTP response headers provide additional metadata.

Return value: (any)

has_dot_args

Usage:

has_dot_args(%args) -> [$status_code, $reason, $payload, \%result_meta]

This function contains arguments with dot in their names.

This function is not exported.

Arguments ('*' denotes required arguments):

  • a.number* => int

    (No description)

  • another.number* => float

    (No description)

Returns an enveloped result (an array).

First element ($status_code) is an integer containing HTTP-like status code (200 means OK, 4xx caller error, 5xx function error). Second element ($reason) is a string containing error message, or something like "OK" if status is 200. Third element ($payload) is the actual result, but usually not present when enveloped result is an error response ($status_code is not 2xx). Fourth element (%result_meta) is called result metadata and is optional, a hash that contains extra information, much like how HTTP response headers provide additional metadata.

Return value: Return the two numbers multiplied (any)

has_duration_arg

Usage:

has_duration_arg(%args) -> [$status_code, $reason, $payload, \%result_meta]

This function contains a duration argument.

This function is not exported.

Arguments ('*' denotes required arguments):

  • duration* => duration

    (No description)

Returns an enveloped result (an array).

First element ($status_code) is an integer containing HTTP-like status code (200 means OK, 4xx caller error, 5xx function error). Second element ($reason) is a string containing error message, or something like "OK" if status is 200. Third element ($payload) is the actual result, but usually not present when enveloped result is an error response ($status_code is not 2xx). Fourth element (%result_meta) is called result metadata and is optional, a hash that contains extra information, much like how HTTP response headers provide additional metadata.

Return value: (any)

HOMEPAGE

Please visit the project's homepage at https://metacpan.org/release/Perinci-Examples.

SOURCE

Source repository is at https://github.com/perlancar/perl-Perinci-Examples.

AUTHOR

perlancar <perlancar@cpan.org>

CONTRIBUTING

To contribute, you can send patches by email/via RT, or send pull requests on GitHub.

Most of the time, you don't need to build the distribution yourself. You can simply modify the code, then test via:

% prove -l

If you want to build the distribution (e.g. to try to install it locally on your system), you can install Dist::Zilla, Dist::Zilla::PluginBundle::Author::PERLANCAR, Pod::Weaver::PluginBundle::Author::PERLANCAR, and sometimes one or two other Dist::Zilla- and/or Pod::Weaver plugins. Any additional steps required beyond that are considered a bug and can be reported to me.

COPYRIGHT AND LICENSE

This software is copyright (c) 2023, 2022, 2020, 2019, 2018, 2017, 2016, 2015, 2014, 2013, 2012, 2011 by perlancar <perlancar@cpan.org>.

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

BUGS

Please report any bugs or feature requests on the bugtracker website https://rt.cpan.org/Public/Dist/Display.html?Name=Perinci-Examples

When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.