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
Logic inverted between GuardAgainstExpression.cs and GuardAgainstExpressionDeprecated.cs
before it was: if (!func(input)) throw now it's: if (func(input)) throw
if (!func(input)) throw
if (func(input)) throw
in tests: before it was : "Value is not equal to 10" now it's: "Value cannot be 10"
"Value is not equal to 10"
"Value cannot be 10"
should imho be mentioned in [Obsolete("Deprecated: Switch to Expression for validation.")]
Steps to Reproduce:
The text was updated successfully, but these errors were encountered:
Good point. I'll update
Sorry, something went wrong.
Update Obsolete message to note reversal of logic.
27e0501
Fixes #356
fbe4c3d
Successfully merging a pull request may close this issue.
Logic inverted between
GuardAgainstExpression.cs
and
GuardAgainstExpressionDeprecated.cs
before it was:
if (!func(input)) throw
now it's:
if (func(input)) throw
in tests:
before it was :
"Value is not equal to 10"
now it's:
"Value cannot be 10"
should imho be mentioned in
[Obsolete("Deprecated: Switch to Expression for validation.")]
all
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: