Pact Spec v4 Files Not Rendered in Broker

[adamrodger]

One big selling point of Pact Specification v4 is that HTTP and messaging (and others....) interactions can all be contained in the same pact file.

However, if you upload a v4 pact to the broker which contains both HTTP and message interactions then the broker fails to parse it and simply falls back to displaying the raw JSON output.

[github-actions]

👋 Hi! The 'smartbear-supported' label has just been added to this issue, which will create an internal tracking ticket in PactFlow's Jira (PACT-1146). We will use this to prioritise and assign a team member to this task. All activity will be public on this ticket. For now, sit tight and we'll update this ticket once we have more information on the next steps.

See our documentation for more information.

[YOU54F]

Hey,

This has been also been case since the V3 spec - from the detail in #127 it sounds like its just the rendering that needs sorting

If anyone would like to collaborate on this, both from coding and from a design perspective, get in touch and we can provide some pointers or have a nice round table :)

[YOU54F]

Also related

• Pact-Broker does not view Pacts with query matching #241
• Render message pacts elegantly #127

[yshunevych-amplify]

Can you guys please revisit the priority of this issue? It's still reproducible, making it harder for us to implement contract testing elegantly. It's a problem for a MessageConsumerPact, which uses pact v3 under the hood