[
https://issues.apache.org/jira/browse/VALIDATOR-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906763#comment-17906763
]
Gary D. Gregory edited comment on VALIDATOR-497 at 12/18/24 2:45 PM:
---------------------------------------------------------------------
I think "checkValid" is better to avoid using names associated with JUnit.
I've been using names like "checkFoo" where Foo is a state like "checkOpen" for
a JDBC connection or a stream.
See also names like CertPathChecker.check() where what is checked is implied by
the class name.
was (Author: garydgregory):
I think "checkValid" is better to avoid using names associated with JUnit.
I've been using names like "checkFoo" where Foo is a state like "checkOpen" for
a JDBC connection or a stream.
> Extends validation result of IBANValidator
> ------------------------------------------
>
> Key: VALIDATOR-497
> URL: https://issues.apache.org/jira/browse/VALIDATOR-497
> Project: Commons Validator
> Issue Type: New Feature
> Reporter: Slawomir Jaranowski
> Priority: Major
> Fix For: 1.10.0
>
>
> Currently we have a method {{IBANValidator#isValid}} which return true or
> false depends on validation result.
> But for false result we don't know a reason, which can be like unsupported
> country, invalid pattern, invalid checksum and so on ...
> Proposition is to add next method which throw exception with more details
> about reason of failed verification.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)