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
Render message pacts elegantly #127
Comments
Hi @bethesque Could you please elaborate on this issue?
Where can I view this document?
I assume that work already done with the HTTP pacts. How can I view such pacts? Sorry, I am new to pacts so those thing may not be trivial to me :). Cheers, |
I've just realised that this issue is not a straightforward one and is not a good first issue after all, because the message pacts use the v3 pact specification, which the Ruby implementation does not know how to parse yet. I have already done a heap of explaining and link finding though, so I'll include them for future reference. If you request the pact URL with `Accept: text/html...", it will give you this nice HTML view of the pact, rather than the JSON. The way it is currently rendered is a bit indirect. It uses some code in the pact-ruby project to create a markdown representation of the pact, and then we turn it into HTML, and wrap it in some extra HTML to render it as a pact broker page. These are the pact resource that render the HTML content type: This is the HTML pact renderer This is the markdown renderer |
This issue is still relevant right? We get the following message on Pact Broker for message pacts:
Does it mean v3 Pacts are also partially supported yet for HTTP pacts? |
I'm not familiar with Ruby but of someone can give some pointers to what/where to modify I'll be happy to help. |
It's only the rendering that is not supported - the content itself is fine. We've actually carded up the work in the Pactflow team's Jira (PACT-523) to do this, but it hasn't been scheduled yet. |
Currently the entire document is rendered as JSON. Format it nicely like the HTTP pacts.
The text was updated successfully, but these errors were encountered: