rholshausen
05/21/2026, 4:59 AMMatt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
rholshausen
05/21/2026, 5:07 AMrholshausen
05/21/2026, 5:09 AMConcrete examples in the proposals may use gRPC for illustration, but the logical interface must not embed transport-specific assumptions
Tien Vo
06/02/2026, 7:30 PMtext/event-stream), or define a fiction content type (e.g. application/test). Can the plugin independent from the content type? maybe related to 006
• Can I define new "standalone" matching rules and generators using plugin? They are not defined in v4 specification, and work with any content types (json, xml, ...), not just the content type the plugin belong to (see the question above). Maybe related to 006 and 009. Btw, I create an rfc for a new 'random array' generator, but no feedback so far (maybe because it's not listed in pulls?), I would love to have ability to create the plugin just for that generator.
• Can we define multiple plugins per interaction? Can we define multiple plugins per integration (each consumer-provider pair)? Look at the pact json structure, maybe the answer is yes for both? I didn't test this kind of behavior before. If the answer is no, I would love this feature, because of the previous question. If I have many standalone matching rules and generators, I would like to use many of them in single interaction.Matt (pactflow.io / pact-js / pact-go)
rholshausen
06/03/2026, 12:05 AMAs I understand, each plugin need to belong to (or related to) a content type (e.g.The design defines different types of plugins. There are plugins that deal with certain types of content (content plugins, and yes, those are related to a content type) and transport plugins (implementing a transport protocol, these may be associated with some type of content, for instance, gRPC requires Protobufs), but there are other types as well that are not associated with any type of content. We haven't created any of these yet.), or define a fiction content type (e.g.text/event-stream). Can the plugin independent from the content type?application/test
rholshausen
06/03/2026, 12:07 AMCan I define new "standalone" matching rules and generators using plugin? They are not defined in v4 specification, and work with any content types (json, xml, ...), not just the content type the plugin belong to (see the question above). Maybe related to 006 and 009. Btw, I create an rfc for a new 'random array' generator, but no feedback so far (maybe because it's not listed in pulls?), I would love to have ability to create the plugin just for that generator.This is in the design, but there is no support implemented for these types of plugins yet.
rholshausen
06/03/2026, 12:08 AMCan we define multiple plugins per interaction? Can we define multiple plugins per integration (each consumer-provider pair)? Look at the pact json structure, maybe the answer is yes for both? I didn't test this kind of behavior before. If the answer is no, I would love this feature, because of the previous question. If I have many standalone matching rules and generators, I would like to use many of them in single interaction.Yes, the design and implementation allows for multiple plugins