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
ShouldBeType<T>() accepts null, while the counterpart ShouldNotBeType<T>() does not. It's not only inconsistent, but also very inconvenient:
ShouldBeType<T>()
ShouldNotBeType<T>()
I don't want my assertion to throw a NullReferenceException, because then I lose the assertion message and have no idea what the error might be.
NullReferenceException
The text was updated successfully, but these errors were encountered:
No branches or pull requests
ShouldBeType<T>()
accepts null, while the counterpartShouldNotBeType<T>()
does not. It's not only inconsistent, but also very inconvenient:I don't want my assertion to throw a
NullReferenceException
, because then I lose the assertion message and have no idea what the error might be.The text was updated successfully, but these errors were encountered: