Hi,
On Wed, 12 Jun 2024 at 17:23, Department 8 <manstein.fe...@gmail.com> wrote:
> Hey!
>
> Recently when using StringUtils in one of our projects I had felt the
> urgent need to have a utility method like => isAnyNotBlank.
>
> I was able to achieve this using the negation of isAllBlank, so I am
> thinking of introducing the code with all tests.
>
> It is ready to be pushed to PR. Do let me know what you think and what are
> the next steps for the same?
>
Is this different from:
public static boolean isAnyNotBlank(final CharSequence... css) {
return !isAllBlank(css);
}
If the implementation is as above then you add an extra method that must be
invoked using more characters than:
!StringUtils.isAllBlank(...)
This doesn't seem helpful. If there is more logic to the method then it may
be worth considering.
There are also the other methods that could be similarly negated:
isAllEmpty
isAllLowerCase
isAllUpperCase
If you are simply negating the result of another method then this use case
may be better served with addition of a suitable example to the javadoc of
the method you are negating.
Alex
