⚠️ currently possible incorrect warnings about valid matchers. Can remove matchers from schema and perform upstream changes later to https://github.com/pactflow/pact-schemas
Have now set matchers, matchingRules, generators to be allowed as property keys but provide no validation, and they are removed from the object mapper.
Processes the following interaction types
V2
V3 sync/http
V3 sync/http
V4 sync/http
⚠️ TODO - explicitly detect and ignore incompatible types
Will filter out non "Synchronous/HTTP" interaction types for v4 pacts.
Creates new scoped option --base-uri / -b for user to provide url override when uploading pacts as Pact's do not contain that info
Creates new scoped option --ignore-pact-schema-verification-result for user to ignore the validation performed against the pact-schemas. The files may, or may not be supported if they fail validation, but allows an escape hatch, just in case it is an issue on our side to fix with the schemas
fixes #10
currently possible incorrect warnings about valid matchers. Can remove matchers from schema and perform upstream changes later to https://github.com/pactflow/pact-schemasTODO - explicitly detect and ignore incompatible types"Synchronous/HTTP"
interaction types for v4 pacts.--base-uri
/-b
for user to provide url override when uploading pacts as Pact's do not contain that info--ignore-pact-schema-verification-result
for user to ignore the validation performed against the pact-schemas. The files may, or may not be supported if they fail validation, but allows an escape hatch, just in case it is an issue on our side to fix with the schemas