-
Notifications
You must be signed in to change notification settings - Fork 46
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
Need to provide more info when a pact merge conflict occurrs #2
Comments
… d22d4667..416f3a64 416f3a64 Fix grammar in README.md bb740850 feat: Add interaction description to the published verification results ec373503 Merge pull request #6 from tienvx/disable-kafka c693b549 chore: Add @wip tag to Kafka scenario db548451 Merge pull request #2 from tienvx/remove-duplicated-scenarios 96c35a0c chore: Remove duplicated scenarios git-subtree-dir: compatibility-suite/pact-compatibility-suite git-subtree-split: 416f3a64d49bee977b0f404a5ba3002eae570eb3
Is this still required or can it be considered complete? There were some improvements in the above commit to provide more granular information on mismatches. It looks like we collect errors and report back message pact errors -
sync pact errors -
do we need to do the same in the v4 merge func pact-reference/rust/pact_matching/src/models/v4/mod.rs Lines 547 to 558 in 118daa1
|
When there is a merge conflict, the consumer test fails with something like
The text was updated successfully, but these errors were encountered: