We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have noticed the noContent assertion when I was about to submit a PR with an isEmpty implementation.
noContent
isEmpty
Why the asserion is called noContent? It does the opposite from notEmpty and IMO the clearest name for this check is isEmpty.
notEmpty
The text was updated successfully, but these errors were encountered:
To preserve backward compatibility, an alias would be needed.
Happy to look at a PR for this.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I have noticed the
noContent
assertion when I was about to submit a PR with anisEmpty
implementation.Why the asserion is called
noContent
? It does the opposite fromnotEmpty
and IMO the clearest name for this check isisEmpty
.The text was updated successfully, but these errors were encountered: