Hi, I am trying to see what changed in the pacts....
# pactflow
r
Hi, I am trying to see what changed in the pacts. I found this documentation on the pactflow website. But when I go into the API of my pact and look into the API, I cannot see
pb:diff-previous-distinct
anywhere. Neither does the
pb:diff
row exist. How can I get that entry to pop up in the HAL Browser?
✅ 1
m
If there is no previous distinct/diff, that would imply there is no previous version I believe
This resource displays the difference between the current pact, and the previous “distinct” version. Given that the pact file does not change every time it is published, the previous distinct version is the most recent version published before the current one where the content is actually different.
r
I am currently looking into a problem that we keep having no verification between the consumer and provider, so the pact seems to change with every publish as there seems to be some generation involved. So I do believe it changes
👍 1
@Matt (pactflow.io / pact-js / pact-go) any other idea why it is not visible for me?
m
Could you maybe show us a video of what you're doing? I've noticed the HAL browser doesn't always take you to the exact URL you're on
r
I cannot easily create a video, but I can send some screenshots: on the left you can see my pact screen, I click on the
API
button in the top right, and then I get to the browser in the second picture
m
Yep, the url on the right shows you're back at the root resource. Copy the pact URL from the left and put it into the HAL navigation, or navigate via the HAL links to the pact you want to diff
(you'll need to first navigate to the pact version)
r
Yes that works, thanks. Where can I give feedback like that? If I am on a page of a pact and click
API
I would expect to actually go to the right document in the HAL Browser instead of the very beginning again 🤔
m
I’ll take that. We are building a new UI right now, so the focus is on that. We will be preserving a HAL browser so will ensure this is covered, albeit perhaps we should be baking this capability into our UI directly. If you could elaborate on your use case more (why do you need to diff, what version are you diffing against etc.) that might help us with that.
r
Of course: I had a pact were the API never changed. still we ran at the
can I deploy
step into a verification problem nearly constantly. When I looked into pactflow, I could see that the verification happened for nearly every published pact, so something must have changed after all. In the end I found out, that we used a generator which then sometimes has
true
in the test request and sometimes
false
and that meant that the pact changed everytime the other value was used. So what I tried to use the HAL browser for was basically What is the change that made this particular pact needing verification again? In the end what I did I manually downloaded the latest version and then the version before and did a manual diff in my IDE I hope this helps. If I need to clarify some more, please do not hesitate to give feedback 🙂
chefkiss 1
m
Very helpful - thank you!
r
no worries, if I can help make it easier usable for me by sharing my needsand my thoughts, I am more than happy to do so
thankyou 1