Matt Fellows
Matt Fellows
Apologies, I somehow missed this - yeah all for that move. If you're up for a PR I'd be happy to accept :)
> Thanks @mefellows for suggesting this! Sorry I'm quite busy over the Christmas period so don't have time to look at this properly right now 🎄 I totally understand! >...
Sorry for my delay in response here, i've been on leave. > (Or, would you still manually call expect(res).toSatisfyApiSpec() for all paths, then at the end call expectOASIsSatisfied() to calculate...
Thanks for this great issue @mkielar! Whilst this change might be worth doing (I'll leave it to those that know more about the query) you may also be interested in...
Very cool! "Selector" also comes to mind, because it's used elsewhere as a sort of filter. But I can see why you may not want to override that term, so...
I love this idea. It does raise some other thought bubbles for me though: * Is it more appropriate to have this information recorded in the pact itself (for example,...
Off the top of my head, this list could include: 1. GraphQL 1. OpenAPI specification (2.0 and 3.0) 1. `.proto` files for teams using protocol buffers / gRPC 1. SOAP...
Ah, I see the initial intent for this was http and message pacts.
Sure, we'd be happy to accept a PR! Like anything, it needs to be maintained. None of the maintainers use Kubernetes day to day, so a build would need to...
Update: Branch is up and working, except there is an issue with message pact on AppVeyor builds that needs further review.