You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
While versioning contracts, we append git branch name to the version so we always have separate contract per branch. Unfortunately, when version contains special characters (like '/' in my case) fetching pacts via PactBrokerClient.fetchLatestConsumersWithNoTag or PactBrokerClient.fetchConsumersWithSelectors fails with au.com.dius.pact.core.pactbroker.NotFoundHalResponse: No HAL document found at path .... For example for response from the broker containing:
PactBrokerClient would go to http://broker-url/pacts/provider/provider.name/consumer/consumer.name/version/3.0.2-SNAPSHOT-feature/123 which is incorrect in this case.
Pact jvm version that we're using is 4.0.10, but I can see nothing has changed in this area on current master.
It seems that href decoding is unnecessary, if you agree (or have other suggestion on how to approach it) then I'm happy to contribute a fix for that.
The text was updated successfully, but these errors were encountered:
uglyog
added
the
bug
Indicates an unexpected problem or unintended behavior
label
Jul 12, 2020
Hello,
While versioning contracts, we append git branch name to the version so we always have separate contract per branch. Unfortunately, when version contains special characters (like '/' in my case) fetching pacts via
PactBrokerClient.fetchLatestConsumersWithNoTag
orPactBrokerClient.fetchConsumersWithSelectors
fails withau.com.dius.pact.core.pactbroker.NotFoundHalResponse: No HAL document found at path ...
. For example for response from the broker containing:PactBrokerClient
would go tohttp://broker-url/pacts/provider/provider.name/consumer/consumer.name/version/3.0.2-SNAPSHOT-feature/123
which is incorrect in this case.Pact jvm version that we're using is 4.0.10, but I can see nothing has changed in this area on current master.
It seems that
href
decoding is unnecessary, if you agree (or have other suggestion on how to approach it) then I'm happy to contribute a fix for that.The text was updated successfully, but these errors were encountered: