You cannot create a pact for an integration that contains both messages and interactions

[jameshalsall]

Pre issue-raising checklist

I have already (please mark the applicable with an x):

• [x] Upgraded to the latest Pact Broker OR
• [ ] Checked the CHANGELOG to see if the issue I am about to raise has been fixed
• [ ] Created an executable example that demonstrates the issue using either a:
  • Dockerfile
  • Git repository with a Travis or Appveyor (or similar) build

Software versions

• pactflow.io

Expected behaviour

When I publish a pact file that contains both "interactions" and "messages" keys, describing both HTTP and async communication, I expect both of these to be visible in the pact details page in the broker.

Actual behaviour

Instead, I can only see the messages in the pact details page.

Steps to reproduce

Define an integration that has both HTTP (sync) and messages (async) communication, publish it to the broker.

Relevant log files

N/A

[bethesque]

It's actually that the message contracts have no UI for them.

Also, defining a pact with both interactions and messages is not supported by any pact library yet. The feature is being discussed here https://github.com/pact-foundation/pact-specification/issues/79