v0.14.0

Add kin-openapi parity features: router, content validation, and OpenAPI 3.2 support

Port key kin-openapi capabilities into libopenapi-validator:

• New router package with route resolution and server matching
• New content package for content-type negotiation and body decoding
• Content-based parameter validation (parameters/content_parameter.go)
• Internal bodycodec and requeststate packages for body/route caching
• Request defaults application (request_defaults.go)
• Validated OpenAPI 3.2 document validation support with new test specs
• Kin parity test suites across paths, requests, responses, and root
• Extended config options and updates across parameters, request,
• response, and schema validation paths.

v0.13.13

Fixed slowdown in new $def schema resource composition at scale, by using a cache, which needs lifecycle management, so in comes the Release() pattern from libopenapi.

Also reorders a prop in a struct, because it was creating a build issue downstream.

@siretart

v0.13.12

bumps to yaml RC6, fixing a bunch of panics across the stack.

v0.13.11

Circular refs supported in schema validation.

Circular references were never allowed in schema validation because the work required to bring references in line was too great. There have been many advances in libopenapi recently that have made this easier.

So, now the schema validator will build all references as inline resources first. This would have been too much work a year ago, but here we are.

Addresses issues #290 an #287

v0.13.10

Fixes #281, fixes tests in from libopenapi bump and moves to our own fork of testify.

v0.13.8

• Reworked request and response schema validation to use errors.As instead of direct JSON Schema error type assertions, making validation error handling safer when errors are wrapped.

• Fixed a goroutine leak in schema-property lookup for empty JSONPath values and added a regression test for that case.

@SebTardif

v0.13.7

Fixes a few issues.

• #258
• #236
• #243

v0.13.6

Fixes issues #83 (an oldie!)

v0.13.5

Addresses

• #227

@vmarceau

v0.13.4

Add opt-in readOnly/writeOnly rejection to strict mode

When StrictRejectReadOnly is enabled, readOnly properties in requests are reported as validation errors instead of being silently skipped. When StrictRejectWriteOnly is enabled, writeOnly properties in responses are reported similarly.

Addresses #90

@byted