New Features:

• Added support for Request Validation. For now, this only includes request body validation and uses the exact same logic as response body validation.
• The FailureType enum has also been updated to include many Request specific types. Check the docs site for the full list.

Bug Fixes:

• Properties were not showing in Failure messages. This was fixed by duplicating the properties in the failure message.

New Features:

• Updated testcase names to include "{method} {path} {correlationId}" to make it easier to see what a testcase is for at a glance.
• Added properties to the tag in the JUnit report to make it easier for people to see what the properties for a testcase are.
• Added correlationId to the properties.

Bug Fixes:

• Using the properties tag within a testcase doesn't seem to be well supported. Instead I've opted to use instead to communicate what the properties for a testcase are. I believe this should be more widely supported.

Bug Fixes:

• I think I messed up the JUnit template when I originally implemented it. Previously the report would start with a element and then start listing the s. This release starts the report with a element, then a element, and then lists the s. This should be the correct format.

Bug Fixes:

• It turns out the proxy would panic if the response body was empty. This has been fixed by trying to get the response body bytes and if that fails, assume there wasn't a body.

Chores:

• Adding documentation pages for Custom Headers, Reports, JUnit, and Contributing Bug Fixes:
• Depending on if you ended the upstream suffix with a / or not, the proxy would not correctly match the operation in the OpenAPI file. This has been fixed so that the proxy will correctly match the operation in the OpenAPI file regardless of an ending / on the upstream URL.

Bug Fixes:

• Entries in the Validation Failures page were missing because the script used to generate the entries required rust nightly. The site build now uses the nightly toolchain to accomodate this.

Chores:

• Fixing the GitHub pages site. I was looking at the wrong default branch.

Chores:

• Trying to put together a GitHub pages site for the project

New Features:

• Support for suffixed upstream url
  • This allows the proxy to work with servers that are mounted at a path other than the root. For example, if your server is mounted at /api/v1 you can run openapi-validator-proxy proxy petstore.yaml http://localhost:8080/api/v1. Make a GET request to http://localhost:3000/api/v1/pets and the proxy will forward the request to http://localhost:8080/api/v1/pets. Validation will match against the GET /pets operation in the OpenAPI file.

New Features:

• Add --version flag to print the version of the binary

Chores:

• Updated README to mention looking for binaries in the releases tab
• Added integration tests
• Add CI workflow to run tests/linting/formatting

Initial release!

The proxy command sort of works to validate requests. This includes functionality that validates:

• path
• HTTP method
• object response bodies
• allOf response properties
• string/boolean/number/array response properties

Results are captured in a Junit report which can be found at localhost:3000/_ovp/junit.

The following errors are also captures in the Junit report:

• PathNotFound,
• InvalidHTTPMethod,
• InvalidStatusCode,
• MissingResponseDefinition,
• MissingContentTypeHeader,
• MismatchedContentTypeHeader,
• MismatchNonEmptyBody,
• MissingSchemaDefinition,
• FailedJSONDeserialization,
• FailedValidationUnexpectedNull,
• FailedValidationUnexpectedBoolean,
• FailedValidationUnexpectedNumber,
• FailedValidationUnexpectedString,
• FailedValidationUnexpectedProperty,
• FailedValidationUnsupportedSchemaKind,