1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
SYNOPSIS
use Perinci::Sub::Util::PropertyModule qw(get_required_property_modules);
my $meta = {
v => 1.1,
args => {
foo => {
...
'form.widget' => '...',
},
bar => {},
},
'cmdline.skip_format' => 1,
result => {
table => { ... },
},
};
my $mods = get_required_property_modules($meta);
Result:
['Perinci::Sub::Property::arg::form',
'Perinci::Sub::Property::cmdline',
'Perinci::Sub::Property::result::table']
FUNCTIONS
get_required_property_modules($meta) => array
Since the Perinci framework is modular, additional properties can be
introduced by additional property modules (Perinci::Sub::Property::*).
These properties might be experimental, 3rd party, etc.
This function can detect which modules are used.
This function can be used during distribution building to automatically
add those modules as prerequisites.
|
