- Fix endless loop on BareSourcelessResultClass->throw_exception(...)
* Misc
+ - Make the Optional::Dependencies error messages cpanm-friendly
- Depend on newer SQL::Abstract (fixing overly-aggressive parenthesis
opener: RT#99503)
- Depend on newer Moo, fixing some interoperability issues:
my $res;
if (keys %errors) {
- my $missing = join (', ', map { $deps->{$_} ? "$_ >= $deps->{$_}" : $_ } (sort keys %errors) );
- $missing .= " (see $class for details)" if $reqs->{$group}{pod};
+ my $missing = join (', ', map { $deps->{$_} ? qq("${_}~>=$deps->{$_}") : $_ } (sort keys %errors) );
+ $missing .= " (see $class documentation for details)" if $reqs->{$group}{pod};
$res = {
status => 0,
errorlist => \%errors,
For example if some of the requirements for C<deploy> are not available,
the returned string could look like:
- SQL::Translator >= $sqltver (see $class for details)
+ "SQL::Translator~>=$sqltver" (see $class documentation for details)
The author is expected to prepend the necessary text to this message before
returning the actual error seen by the user.
like (
DBIx::Class::Optional::Dependencies->req_missing_for ('deploy'),
- qr/^SQL::Translator \>\= \d/,
+ qr/
+ (?: \A|\s )
+ " SQL::Translator \~ \>\= [\d\.]+ "
+ \s
+ .*?
+ \Q(see DBIx::Class::Optional::Dependencies documentation for details)\E
+ \z
+ /x,
'expected missing string contents',
);