File Coverage

blib/lib/Sah/PSchema/re_from_str.pm

Criterion	Covered	Total	%
statement	3	7	42.8
branch	0	2	0.0
condition	0	2	0.0
subroutine	1	3	33.3
pod	0	2	0.0
total	4	16	25.0

package Sah::PSchema::re_from_str;

use strict;

our $AUTHORITY = 'cpan:PERLANCAR'; # AUTHORITY
our $DATE = '2024-05-30'; # DATE
our $DIST = 'Sah-PSchemaBundle-Re'; # DIST
our $VERSION = '0.003'; # VERSION

sub meta {
    return +{
        v => 1,
        args => {
            always_quote => {
                summary => 'Passed to Regexp::From::String\'s str_to_re()',
                schema => 'bool*',
            },
            case_insensitive => {
                summary => 'Passed to Regexp::From::String\'s str_to_re()',
                schema => 'bool*',
            },
            anchored => {
                summary => 'Passed to Regexp::From::String\'s str_to_re()',
                schema => 'bool*',
            },
        },
    };
}

sub get_schema {
    my ($class, $args, $merge) = @_;
    return [re => {
        summary => 'Regexp object from string using Regexp::From::String\'s str_to_re()',
        description => <<'_',

This schema accepts Regexp object or string which will be coerced to Regexp object
using 's `str_to_re()` function.

Basically, if string is of the form of `/.../` or `qr(...)`, then you could
specify metacharacters as if you are writing a literal regexp pattern in Perl.
Otherwise, your string will be `quotemeta()`-ed first then compiled to Regexp
object. This means in the second case you cannot specify metacharacters.

_

        prefilters => [ ['Re::re_from_str'=>($args || {})] ],

        examples => [
        ],
        %{ $merge || {} },
    }];
}

1;
# ABSTRACT: Regexp object from string (parameterized)

__END__