-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
isNotNullOrEmpty() for Iterables #512
Comments
I don't think they should be combined. One is a general assertion which refines the type, whereas the other is an assertion on the contents of a collection. |
I believe it could be treated as the inverted of |
That assertion is impossible to otherwise represent though. It requires #450. Asserting not null or empty is worded as |
Reasonable. It looks like |
Currently the official way in the documentation is to first call
.isNotNull()
and then.isNotEmpty()
. Can there be a new method that combines them? I know you can write a custom assertion but would be nice to have it built-in. Happy to open a pull request.Example:
from:
to:
The text was updated successfully, but these errors were encountered: