-
Notifications
You must be signed in to change notification settings - Fork 47
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
merging sync message interaction, in existing pact, alters existing interaction content. #473
Comments
We might be able to tackle #467 at the same time, to whomever is looking at the merging logic |
So I have been debugging this, and the Pact merging logic is doing the correct thing. This is not the correct form:
When merging, the previous Pact is loaded and corrected (in fact, it is loaded as an Empty body, and that has no other attributes so the other ones are dropped). |
I think the error is in the plugin driver, it is not encoding an empty body correctly. |
Thanks Ron! |
Changeset: pact-foundation/pact-reference@libpact_ffi-v0.4.23...libpact_ffi-v0.4.26 Notable New Features - pact-foundation/pact-reference#478 - pact-foundation/pact-reference#479 - pact-foundation/pact-reference#462 Notable Fixes - pact-foundation/pact-reference#473
Summary
A pact-ruby-ffi user noted an issue with modifications in tried pact file, which was causing errors when trying to upload to a broker with the same, as the contents were modified inadvertently, thus triggering Pact Brokers dangerous modification of contracts block, stopping the user from uploading their pact file
Originally noted in YOU54F/pact-ruby-ffi#6
Reproduction Steps
expected: 2 interactions are generated, identical bar interaction description
actual: existing interaction is modified at response[0].contents, when merging 2nd interaction
Detail
Merging of the new interaction with an existing pact, results in the first interaction losing some fields, transforming the first interaction from
to
with a diff of
Code Reproduction
test case added to pact_ffi suite in commit - YOU54F@3e0b6ec
Test Output
## Relevant logs
Issue occurs when invoking the write pact function. Somewhere in these function calls
The text was updated successfully, but these errors were encountered: