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