Fix matching of multiple expected zoned date/time values with multiple actual local ones #2650
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, Wiremock doesn't support matching multiple expected zoned date/time values with multiple actual local ones.
In other words, given the matchers below:
Then a GET request to the URL below should match (assuming the date is March 27th 2024):
/resource?date=2024-03-27&date=2024-03-28
Instead, we get a "request was not matched" message.
This PR add supports for the above scenario and also adds two test cases which fail with the current implementation.
References
An older, related PR: #1925
Submitter checklist
#help-contributing
or a project-specific channel like#wiremock-java