v0.2.2

Swapped out a boolean channel for a struct{} which uses no memory.

@baerwang

v0.2.1

Fixes issue with validation failing on empty security definitions. Fixes #97

@AidanWelch

v0.2.0

No new features, but does upgrade latest deps (libopenapi) https://github.com/santhosh-tekuri/jsonschema to v0.6.1 Which improves all schema handling. A few tune ups were required, error messages are slightly different now and there is less noise in the machine.

Also added coverage across the project to level up quality.

v0.1.0

This is a breaking change release that refines some of the behavior of the library.

SetPathItem was removed from the parameter validation. It was causing race conditions.

• #87

The FindPath method no-longer performs any validation, it was a mix of concerns.

• #72

@emilien-puget

v0.0.56

Addresses a panic when response code ranges are used, also addresses issue #78 where missing path params were being ignored.

@k1LoW @budanm

v0.0.55

Adds a new synchronous version of ValidateHttpRequest called ValidateHttpRequestSync

#79

@commoddity

v0.0.54

Fixes an issue with parameter schema validation was not rendering inline, so $ref values were not being resolved correctly.

Also bumps libopenapi version.

v0.0.53

Fixes issue with body validation.

• #75

v0.0.52

Fixes an issue with path param validation that didn't pass through the rendered schema with the validation error.

Also added in a couple of nil pointer exception catches and bumped deps.

No new features.

v0.0.51

1. Introduces improved error handling for the JSON schema compilation process in the request validation logic. Previously, the code did not handle potential errors from the compiler, which caused the code to panic when attempting to validate the request body.

The change will improve reliability by ensuring that schema compilation errors are gracefully handled, thus improving the stability of the request body schema validation process. Additionally, this will facilitate quicker debugging and resolution of issues related to invalid schemas.

2. Request bodies are optional by default.
   see https://spec.openapis.org/oas/v3.1.0#fixed-fields-10 or https://swagger.io/docs/specification/describing-request-body/
   this dear library doesn't handle such cases
   https://github.com/pb33f/libopenapi-validator/blob/688b7a2e81d820bed7d96b28af6fdebd3d52cea9/requests/validate_body.go#L41

as we can see above, if an operation has a request body, we will require to have a content type set, however that request body could be not required which means that a content type should not be required.

@martinsirbe @emilien-puget