Modules§
- body
- Nested message and enum types in
Body. - catalogue_
entry - Nested message and enum types in
CatalogueEntry. - field_
value - Nested message and enum types in
FieldValue. - generate_
content_ request - Nested message and enum types in
GenerateContentRequest. - init_
plugin_ response - Nested message and enum types in
InitPluginResponse. - interaction_
response - Nested message and enum types in
InteractionResponse. - metadata_
value - Nested message and enum types in
MetadataValue. - pact_
plugin_ client - Generated client implementations.
- pact_
plugin_ server - Generated server implementations.
- plugin_
host_ client - Generated client implementations.
- plugin_
host_ server - Generated server implementations.
- start_
mock_ server_ response - Nested message and enum types in
StartMockServerResponse. - verification_
preparation_ response - Nested message and enum types in
VerificationPreparationResponse. - verification_
result_ item - Nested message and enum types in
VerificationResultItem. - verify_
interaction_ response - Nested message and enum types in
VerifyInteractionResponse.
Structs§
- Body
- Message representing a request, response or message body
- Catalogue
- Catalogue of Core Pact + Plugin features
- Catalogue
Entry - Entry to be added to the core catalogue. Each entry describes one of the features the plugin provides. Entries will be stored in the catalogue under the key “plugin/$name/$type/$key”.
- Compare
Contents Request - Request to preform a comparison on an actual body given the expected one
- Compare
Contents Response - Response to the CompareContentsRequest with the results of the comparison
- Configure
Interaction Request - Request to configure/setup an interaction so that it can be verified later
- Configure
Interaction Response - Response to the configure/setup an interaction request
- Content
Mismatch - A mismatch for an particular item of content
- Content
Mismatches - List of content mismatches
- Content
Type Mismatch - Indicates that there was a mismatch with the content type
- Field
Value - A single value being matched or generated at the field/element level.
- Generate
Content Request - Request to generate the contents using any defined generators
- Generate
Content Response - Generated body/message response
- Generate
Field Request - Request to generate a single value using a plugin-provided generator. Generators are pure functions of this request: anything from the host they need arrives in testContext or is fetched with an explicit callback. See proposal 006.
- Generate
Field Response - Response to the GenerateFieldRequest with the generated value
- Generator
- Example generator
- Host
Compare Contents Request - Callback request from a plugin to invoke a content matcher capability - host-provided or owned by another plugin - resolved by catalogue entry key. See proposal 007 (Driver-plugin callback model).
- Host
Generate Content Request - Callback request from a plugin to invoke a content generator capability - host-provided or owned by another plugin - resolved by catalogue entry key. See proposal 007 (Driver-plugin callback model).
- Host
Generate Field Request - Callback request from a plugin to invoke a field-level generator - host-provided or owned by another plugin - resolved by catalogue entry key. See proposals 006 and 007.
- Host
Match Field Request - Callback request from a plugin to invoke a field-level matching rule - host-provided (one of the standard Pact rules) or owned by another plugin - resolved by catalogue entry key. See proposals 006 (Field-level matchers and generators) and 007 (Driver-plugin callback model).
- Init
Plugin Failure - Failure result of initialising the plugin
- Init
Plugin Request - Request to verify the plugin has loaded OK
- Init
Plugin Response - Response to init plugin, providing either the negotiated success response or a structured failure
- Init
Plugin Success - Successful result of initialising the plugin
- Interaction
Contents - Structured interaction data sent to V2 plugins in place of raw pact JSON. Contains only the data the plugin needs, eliminating the need for plugins to parse full Pact documents.
- Interaction
Data - Interaction request data to be sent or received for verification
- Interaction
Response - Response to the configure/setup an interaction request
- LogMessage
- Structured log record emitted by a plugin and forwarded to the driver via the Log RPC
- Match
Field Request - Request to apply a plugin-provided matching rule to a single value. The plugin sees the value, its path and the rule’s own configuration, but not the document that contains it - a rule that needs the surrounding document is a content matcher. See proposal 006.
- Match
Field Response - Response to the MatchFieldRequest with the result of applying the rule
- Matching
Rule - Represents a matching rule
- Matching
Rules - List of matching rules
- Metadata
Value - Request metadata value. Will either be a JSON-like value, or binary data
- Mock
Server Details - Details on a running mock server
- Mock
Server Request - Request for a running mock server by ID
- Mock
Server Result - Result of a request that the mock server received
- Mock
Server Results - Matching results of the mock server.
- Plugin
Configuration - Plugin configuration added to the pact file by the ConfigureInteraction step
- Start
Mock Server Request - Request to start a mock server
- Start
Mock Server Response - Response to the start mock server request
- Verification
Preparation Request - Request to prepare an interaction for verification
- Verification
Preparation Response - Response for the prepare an interaction for verification request
- Verification
Result - Result of running the verification
- Verification
Result Item - Verify
Interaction Request - Request data to verify an interaction
- Verify
Interaction Response - Result of running the verification