Changelog

• 2986a91 Bump the npm_and_yarn group across 1 directory with 1 update

Changelog

• 3705730 deps!

Changelog

• 119ecd7 tune performance and add harific into the family.

Changelog

• a84594f address #142
• 2e337d3 bump deps and fix engine encoding for non JSON content types
• 6903cbd remove yarn.
• 5f4fbb3 update make command

Changelog

• dc8011e Addressed issue #166

Changelog

• a547060 bump all npm deps.
• e4deddd bump deps
• cc3e60b updated to latest API from validator

Changelog

• dd0ded5 fix: invalid arguments in sms.Logger
• 4884579 fix: mock server fails to handle form encoded POST request payload
• d612264 fix: review

wiretap can be configured to enable strict validation that detects undeclared properties, parameters, headers, and cookies. This mode goes beyond standard OpenAPI validation by reporting values that aren’t explicitly documented in the specification, even when additionalProperties: true would normally allow them.

Strict mode is designed for API governance scenarios where you want to ensure that clients only send properties that are explicitly documented in the OpenAPI specification, helping maintain a clean and well-documented API surface.

Even if the JSON Schema for an object has not defined a param as required, or the schema uses additionalProperties strict mode will not care. Anything in the payload that is not explicitly defined in the contact will be flagged as undeclared

When enabled, strict mode detects:

• Undeclared properties
• Undeclared query parameters
• Undeclared request headers
• Undeclared response headers
• Undeclared cookies
• Enabling strict mode

To enable strict mode, use the --strict-mode flag:

https://pb33f.io/wiretap/configuring/#strict-mode

Changelog

• 84a706a Added —strict-mode
• 1331d44 fixed bored go.mod
• e7033dc fixed hard validation mode and strict mode mismatch.

Changelog

• e5e7750 fix docker build

Changelog

• 88c8272 upgraded deps