Fix/pact merge v4 without provider states #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…chings with multi interactions in one file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
todo
add test for merging pact duplicate interactions where existing pact contains multiple unique interaction types
to repro Pact Merging Creates Duplicate Interactions pact-foundation/pact-reference#389 in pact_models (currently reproing, by copying built release binary to pact-net, and running tests locally. Prior exectution would result in
Fulfilment API-Orders API.jsonhaving duplicated interactions on each separate test invocation)cleanup commented out print statements (replace with debugs for troubleshooting later?)
check