-
This plugin currently supports grpc request/response metadata when doing grpc services.
It would be great if it also supported metadata with the proto messages too.
Our particular use-cases is aro…
-
Hi @ptrthomas
From this question https://stackoverflow.com/questions/77346337/karate-test-framework-are-there-plans-to-include-runtimehooks-for-mockserver we open this issue.
In our case, we n…
-
It's very helpful to use mocks for functional testing as a base for consumer contract.
Would be nice to support generation of Pact files from Playwright mocks similarly to how it's done for Cypress.
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Feature Test To Be Requested
Hey,
Great repo
-
> Not having to create our own content type to add metadata to contracts. We have had to make the "application/json" content matcher again so that we can add metadata fields into the contract. This me…
-
Currently, a gRPC Google Struct is used to model values, and these structs only support numeric types in double precision floating point format. It means that any integer values need to be converted t…
-
Being able to configure metadata matching at one or more levels deep and ignoring additional keys would also help us configure the metadata in contracts how we want to.
Ref: https://pact-foundation…
-
Currently, only one set of matching rules can be configured. Need to be able to support matching rules against different targets.
> Configure interaction to support metadata matching rules. This no…
-
Currently, plugin logs to standard output are captured and logged via the calling frameworks logging. This can make it hard to separate from normal logs and pact logs, esp at trace level.
> For me …
-
From https://swagger.io/specification/v3/?sbsearch=readOnly
> Relevant only for Schema "properties" definitions. Declares the property as "read only". This means that it MAY be sent as part of a re…