swagger-mock-validator - npm Package Versions

4.0.0 (2018-04-13)

Bug Fixes

• format validators for int32, int64, float and double no longer accept spaces and now test for the full range of accepted values (a38b085), closes #67

BREAKING CHANGES

• Prior to this change the tool used to accept blank spaces in path parameters for int32, int64, float and double formatted numbers. A bug has been fixed to disallow blank spaces. This means some mock responses that were previously considered valid will now be considered invalid. This change has also updated the int64 and double format validators to now test for the full range of values these types support. This means some mock responses that were previously considered invalid will now be considered valid.

It is recommended that consumers and providers coordinate upgrading to this release so that both sides agree on what is considered valid vs invalid.

<a name="3.0.0"></a>

3.0.0 (2018-01-31)

Bug Fixes

• content negotiation between request content type header and consumes values in spec (100aaf3)

BREAKING CHANGES

• This release contains a bug fix for the way content type headers were being validated. As a result of this bug fix some mocks and specs which were previously considered valid will now be considered invalid.

<a name="2.2.3"></a>

2.2.3 (2017-12-21)

Bug Fixes

• bump swagger-tools to resolve issue where the tool locks up when swagger examples contain a length property (46dac30)

<a name="2.2.2"></a>

2.2.2 (2017-11-29)

Bug Fixes

• reverting fix for content negotiation, this will be re-released as a major version (c72993f)

<a name="2.2.1"></a>

2.2.1 (2017-11-29)

Bug Fixes

• fix content negotiation between request content type header and consumes values in spec (4953743)

<a name="2.2.0"></a>

2.2.0 (2017-09-01)

Features

• add javascript api (ea0f098)

<a name="2.1.0"></a>

2.1.0 (2017-08-07)

Features

• allow empty pact list to be returned from pact broker (1eea0ee), closes #63

<a name="2.0.2"></a>

2.0.2 (2017-07-14)

Bug Fixes

• spec warnings were not shown if mock validation returns errors (c1328a8)

<a name="2.0.0"></a>

2.0.0 (2017-07-11)

Bug Fixes

• allOf validation ignoring required properties and formats (bae1bb7), closes #32

Features

• add support for circular references in the swagger file (dd61f7b), closes #60
• only output mockDetails and specDetails when they relevant (8486bf8), closes #56

BREAKING CHANGES

• Prior to this change the tool used to disallow additional properties in response mocks unless the schema explicitly allowed additional properties. To support the allOf keyword correctly this behavior has been changed. Now additional properties are allowed in response mocks unless a schema explicitly disallows them. This means some mock responses that were previously considered invalid will now be considered valid. It is recommended that consumers and providers coordinate upgrading to this release so that both sides agree on what is considered valid vs invalid.
• swagger-mock-validator now supports validating schemas containing circular references. Prior to this change schemas containing circular references were ignored. If you have a schema that contains circular references and a mock that is not compatible with that schema the swagger-mock-validator will now fail. It is recommended that consumers and providers coordinate upgrading to this release so that both sides agree on what is considered valid vs invalid.

<a name="1.0.0"></a>

1.0.0 (2017-03-24)

Bug Fixes

• the order of security requirements impacts validation results (07a7122)

Features

• add opt-in analytics (6439444), closes #54
• rename project to swagger-mock-validator (2594491), closes #16

BREAKING CHANGES

• The name of the module has changed from “@atlassian/swagger-pact-validator” to “swagger-mock-validator”. To migrate you need to rename the dependency in your package.json and update any code that invokes this cli took from “swagger-pact-validator” to “swagger-mock-validator”.

<a name="0.0.31"></a>