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

v0.0.50

Moved internal cache to sync.Map in response body validator

url.Parse does not handle special characters well.

Some openapi server configurations will have variable templating (ie. {host}). Adds a second parsing attempt if the initial attempt fails by attempting to remove the host.

@jacobm-splunk @k1LoW

v0.0.49

This fix supports the range definition for response codes.

ref: https://swagger.io/docs/specification/describing-responses/

Also fixes a race condition discovered in vacuum when running tests

Response code range fix added by @k1LoW

v0.0.48

Added the following properties to ValidationError

SpecPath = the spec path of the error
RequestMethod = HTTP verb used in the error
RequestPath = HTTP path used in the error

@jacobm-splunk

v0.0.47

Supports / for server definitions now when looking up paths, Fixes a bug with missing security schemes also.

@k1LoW @emilien-puget

v0.0.46

Bugfix to prevent base paths from being altered accidentally.

@k1LoW

v0.0.45

Path parameter validation did not properly strip the base path from the request path when doing parameter validation.

If the server had a non-null postfix path, then the incorrect parameter would be validated.

@jacobm-splunk

v0.0.44

String and number path param validation has been improved.

@emilien-puget

v0.0.43

Add the support to validate query simple params like

parameters:
  - name: fishy
    in: query
    required: true
    schema:
      type: string
      minLength: 4

parameters:
  - name: fishy
    in: query
    required: true
    schema:
      type: number
      minimum: 200

@emilien-puget

v0.0.42

Addressed issue #48