Releases: pb33f/libopenapi
v0.15.0
Adds full windows support to libopenapi, and any application using it. The index module can now make sense of windows paths and drives.
- Addresses #226
- Addresses #218
- Addresses daveshanley/vacuum#417
New Feature
A new bundler
module has been added that contains two new functions. BundleDocument()
and BundleBytes()
Both methods will render out a new OpenAPI
file has all references inlined, all external references, everything.
If you have been looking for a simple way to create a single OpenAPI document, from an whole bunch of referenced files? Then the bundler is what you need.
v0.14.7
v0.14.6
No new features, a small bugfix was added from the community to add missing line and column values to enum
changes in the what-changed
module.
Contribution from: @Amitrei
v0.14.5
No new features, however a deeper check for circular references was added after being discovered in the wild. Also the RootNode
and KeyNode
values of all low level model objects are now available.
Added a check to prevent run-away schema rendering when operating recursively.
Added a timeout guard to any JSON Path lookups in utils.
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
v0.14.1
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