Skip Menu |

This queue is for tickets about the Type-Tiny CPAN distribution.

Report information
The Basics
Id: 131756
Status: open
Priority: 0/
Queue: Type-Tiny

People
Owner: Nobody in particular
Requestors: Th.J.v.Hoesel+CPAN [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: (no value)
Fixed in: (no value)



Subject: Types::Common::String reporting deeper problems
If I have a `NonEmptyStr` constraint violation , it always reports it with "Must not be empty ...". This happens for `undef`, references or an empty string. With a constraint like `Str`, it would report on different levels: - Undef did not pass constraint "Str" - Reference ... did not pass constraint "Str" I would had expected same kind of behaviour, reporting the deeper level violations instead of only the top level
It just gives the same error messages as MooseX::Types::Common::String. Whether exact compatibility at the error message level is desirable or not is debatable.