v0.14.4

Removed the JSONParsingChannel concept completely.

It's the source of a number of problems, when it comes to multi-tenancy and race conditions. It's toast. Good riddance.

v0.14.3

Fixed issue reported in daveshanley/vacuum#400

Added a safety check to prevent an overflow. No new features.

v0.14.2

Fixes #215

v0.14.1

Fixes edge case in Schema() low level model that was not carrying through context correctly when building against exploded references.

Reported in #219

v0.14.0

A major update to libopenapi.

ALL maps are now ordered maps in the datamodel

This is a major breaking change to all users of the datamodel. Examples are now also exposed as raw *yaml.Node elements, vs any

Picks up from #138 and tries to address #119

• Support iterating through the high model in the same order as the OpenAPI document
• Render documents out deterministically
• Render documents out matching the original order (if just making light modifications to the document)
• Control the order of the rendered out docs, for example when the order of path items or components are specifically reordered
• Any maps stored within example or examples fields in schemas can maintain order both on read/write

@TristanSpeakEasy @Baliedge

v0.13.22

Fixes a deadlock issue discovered by vacuum.

daveshanley/vacuum#393

No new features.

v0.13.21

Multiple glitch fixes found whilst testing in the wild.

v0.13.19

Builds on v0.13.18 by adding the issues to both resolving errors and circular errors available on the resolver. This will allow vacuum and other apps to report on the problem effectively.

no new features or fixes.

v0.13.18

Added a safety check to the resolver, it prevents a runaway stack overflow from occurring when nodes are caught in loops do to circular references. No new features, just a more stable library.

v0.13.17

Fixes an issue with the resolver not mapping every reference that is a duplicate. It's an obscure bug, but was picked up by vacuum. No new features, just guaranteed reference resolving.