We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sample (modified) but discovered by the V2 specs from the terraform client
{ "consumer": { "name": "terraform-client" }, "interactions": [ { "description": "a request to create a system account", "request": { "method": "GET", "path": "/foo" }, "response": { "matchingRules": { "$.header.Example": { "match": "type" } }, "headers": { "Example": "value" }, "status": 200 } } ], "metadata": { "pactRust": { "ffi": "0.4.16", "mockserver": "1.2.5", "models": "1.1.19" }, "pactSpecification": { "version": "2.0.0" } }, "provider": { "name": "pactflow-application-saas" } }
The field should be $.headers.<key> not $.header.<key> as per https://github.com/pact-foundation/pact-specification/blob/version-2/testcases/response/headers/matches%20with%20regex.json#L10.
$.headers.<key>
$.header.<key>
The text was updated successfully, but these errors were encountered:
pact-foundation/pact-go#426
Sorry, something went wrong.
This has been around for a very long time. It was fixed in Pact-JVM in 2019 pact-foundation/pact-jvm#882
fix(pact_models): fix: when writing pact specs in V2 format, header m…
77814ae
…atchers must be pluralised #449
No branches or pull requests
Sample (modified) but discovered by the V2 specs from the terraform client
The field should be
$.headers.<key>
not$.header.<key>
as per https://github.com/pact-foundation/pact-specification/blob/version-2/testcases/response/headers/matches%20with%20regex.json#L10.The text was updated successfully, but these errors were encountered: