wrap-with-perinci-sub-wrapper - Wrap subroutine with Perinci::Sub::Wrapper
This document describes version 0.110 of wrap-with-perinci-sub-wrapper (from Perl distribution App-PerinciUtils), released on 2017-08-09.
Usage:
% wrap-with-perinci-sub-wrapper [options] [meta] [args]
This script is useful for testing Perinci::Sub::Wrapper. You specify input Rinci metadata either using --meta or using --url to get it from Riap URL.
--meta
--url
You then can show the code generated by the wrapper using --show-code (-c).
--show-code
-c
Or, you can call the wrapped function with one or more sets of arguments, by supplying --code and one of: --args, --multiple-args, --args-file, or --multiple-args-file.
--code
--args
--multiple-args
--args-file
--multiple-args-file
* marks required options.
*
Don't call sub or wrap, show normalized metadata (before wrapping) only.
Don't call sub, show generated wrapper code only.
Don't call sub, show generated metadata after wrapping only.
Give hint for args file type.
Valid values:
["json","yaml"]
Retrieve args from file.
JSON and YAML formats are supported. File type will be guessed from filename, defaults to JSON.
See --args.
Retrieve multiple args from file.
This is like `args_file` except that for multiple args. Content must be an array.
Call with multiple args (array of args) (JSON-encoded).
See --multiple-args.
Call with multiple args (array of args).
Specify Perl code to wrap.
Set path to configuration file.
Can be specified multiple times.
Set configuration profile to use.
Do not use any configuration file.
Do not read environment for default options.
Specify function metadata (JSON-encoded).
See --meta.
Specify function metadata.
Use function metadata from Riap URL.
Show args alongside with call result.
The default is to show the call result only.
Choose output format, e.g. json, text.
Default value:
undef
Set output format to json.
When showing source code (--show-wrap-code), add line numbers.
When outputing as JSON, add result envelope.
By default, when outputing as JSON, the full enveloped result is returned, e.g.:
[200,"OK",[1,2,3],{"func.extra"=>4}]
The reason is so you can get the status (1st element), status message (2nd element) as well as result metadata/extra result (4th element) instead of just the result (3rd element). However, sometimes you want just the result, e.g. when you want to pipe the result for more post-processing. In this case you can use `--naked-res` so you just get:
[1,2,3]
Whether to generate code which avoids the use of non-core modules.
Whether to generate code which avoids the use of non-core XS modules.
In other words, generated code should stick with core or pure-perl modules.
Whether to generate code which avoids the use of XS modules.
Generate wrapper with debug on.
This means e.g. to pepper the wrapper code with more comments.
Display help message and exit.
Display program's version and exit.
This script has shell tab completion capability with support for several shells.
To activate bash completion for this script, put:
complete -C wrap-with-perinci-sub-wrapper wrap-with-perinci-sub-wrapper
in your bash startup (e.g. ~/.bashrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.
It is recommended, however, that you install modules using cpanm-shcompgen which can activate shell completion for scripts immediately.
To activate tcsh completion for this script, put:
complete wrap-with-perinci-sub-wrapper 'p/*/`wrap-with-perinci-sub-wrapper`/'
in your tcsh startup (e.g. ~/.tcshrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.
It is also recommended to install shcompgen (see above).
For fish and zsh, install shcompgen as described above.
This script can read configuration files. Configuration files are in the format of IOD, which is basically INI with some extra features.
By default, these names are searched for configuration filenames (can be changed using --config-path): ~/.config/wrap-with-perinci-sub-wrapper.conf, ~/wrap-with-perinci-sub-wrapper.conf, or /etc/wrap-with-perinci-sub-wrapper.conf.
--config-path
All found files will be read and merged.
To disable searching for configuration files, pass --no-config.
--no-config
You can put multiple profiles in a single file by using section names like [profile=SOMENAME] or [SOMESECTION profile=SOMENAME]. Those sections will only be read if you specify the matching --config-profile SOMENAME.
[profile=SOMENAME]
[SOMESECTION profile=SOMENAME]
--config-profile SOMENAME
You can also put configuration for multiple programs inside a single file, and use filter program=NAME in section names, e.g. [program=NAME ...] or [SOMESECTION program=NAME]. The section will then only be used when the reading program matches.
program=NAME
[program=NAME ...]
[SOMESECTION program=NAME]
Finally, you can filter a section by environment variable using the filter env=CONDITION in section names. For example if you only want a section to be read if a certain environment variable is true: [env=SOMEVAR ...] or [SOMESECTION env=SOMEVAR ...]. If you only want a section to be read when the value of an environment variable has value equals something: [env=HOSTNAME=blink ...] or [SOMESECTION env=HOSTNAME=blink ...]. If you only want a section to be read when the value of an environment variable does not equal something: [env=HOSTNAME!=blink ...] or [SOMESECTION env=HOSTNAME!=blink ...]. If you only want a section to be read when an environment variable contains something: [env=HOSTNAME*=server ...] or [SOMESECTION env=HOSTNAME*=server ...]. Note that currently due to simplistic parsing, there must not be any whitespace in the value being compared because it marks the beginning of a new section filter or section name.
env=CONDITION
[env=SOMEVAR ...]
[SOMESECTION env=SOMEVAR ...]
[env=HOSTNAME=blink ...]
[SOMESECTION env=HOSTNAME=blink ...]
[env=HOSTNAME!=blink ...]
[SOMESECTION env=HOSTNAME!=blink ...]
[env=HOSTNAME*=server ...]
[SOMESECTION env=HOSTNAME*=server ...]
List of available configuration parameters:
args (see --args) args_file (see --args-file) args_file_type (see --args-file-type) args_with_result (see --args-with-result) code (see --code) core (see --core) core_or_pp (see --core-or-pp) format (see --format) linenum (see --linenum) meta (see --meta) multiple_args (see --multiple-args) multiple_args_file (see --multiple-args-file) naked_res (see --naked-res) pp (see --pp) show_meta (see --show-meta) show_wrap_code (see --show-wrap-code) show_wrap_meta (see --show-wrap-meta) url (see --url) validate_args (see --no-validate-args) validate_result (see --no-validate-result) with_debug (see --with-debug) wrap (see --wrap)
Specify additional command-line options.
~/.config/wrap-with-perinci-sub-wrapper.conf
~/wrap-with-perinci-sub-wrapper.conf
/etc/wrap-with-perinci-sub-wrapper.conf
Please visit the project's homepage at https://metacpan.org/release/App-PerinciUtils.
Source repository is at https://github.com/perlancar/perl-App-PerinciUtils.
Please report any bugs or feature requests on the bugtracker website https://rt.cpan.org/Public/Dist/Display.html?Name=App-PerinciUtils
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.
perlancar <perlancar@cpan.org>
This software is copyright (c) 2017, 2016, 2015 by 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.
To install App::PerinciUtils, copy and paste the appropriate command in to your terminal.
cpanm
cpanm App::PerinciUtils
CPAN shell
perl -MCPAN -e shell install App::PerinciUtils
For more information on module installation, please visit the detailed CPAN module installation guide.