-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
OR matcher no longer accepts null example value #1281
Comments
uglyog
pushed a commit
that referenced
this issue
Jan 10, 2021
uglyog
pushed a commit
that referenced
this issue
Jan 10, 2021
I've used version 4.1.14 and the issue is gone. Thanks! |
This was referenced Mar 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On the 3.x Pacts DSL version I used to have a contract defined like
...where the
failureCode
variable was either populated or null depending on the test case variant executed.The
nonEmptyString()
is my custom method based returning configured regex matcher (irrelevant to the issue).I've just updated to the 4.1.x Pact libs and the
or()
matcher throwsIllegalArgumentException
when the example value is null.What is the way now to declare a contract which says: expect some value of certain format or null?
The text was updated successfully, but these errors were encountered: