Skip to content

Releases: pb33f/libopenapi

v0.16.4

30 Apr 13:11
Compare
Choose a tag to compare

Fixes a regression in the index where examples were being indexed as schemas.

@TristanSpeakEasy

v0.16.3

29 Apr 16:03
Compare
Choose a tag to compare

Fixes a panic when mis-using a reference. No new features.

v0.16.2

22 Apr 23:21
Compare
Choose a tag to compare

This fixes an issue where the MediaType.Example field was being populated when it shouldn't.

It was basically searching down into the schema and other places as well to find an example where it should have only been searching the top level node

@TristanSpeakEasy

v0.16.1

21 Apr 13:12
Compare
Choose a tag to compare

Fixes a couple of bugs reported in vacuum

v0.16.0

19 Apr 10:49
Compare
Choose a tag to compare

No new features, just bugfixes with a very small breaking change (hence the minor bump)

Fixes for the following:

The high/v3/Document struct method RenderJSON now returns an error along with the bytes, this is a very small but breaking change.

v0.15.15

08 Apr 10:35
Compare
Choose a tag to compare

Fixed floating point rendering issue as documented here:

#270

@emilien-puget

v0.15.14

28 Feb 18:17
Compare
Choose a tag to compare

Fixes a bug if there is no model generated when bundling, prevents a panic from being thrown.

@emilien-puget

v0.15.13

21 Feb 13:30
Compare
Choose a tag to compare

When resolving complex, recursive and deep references, The depth counter was being artificially inflated with highly complex recursive designs, this fixes the depth counter permanently and makes sure that after the resolver is done exploring a branch, it decrements the counter correctly, instead of just inflating it over and over.

Fixes issue: #256

v0.15.12

20 Feb 18:41
Compare
Choose a tag to compare

Another round of resolving tuning. Deeply nested objects were sometimes still getting muddled with stage two resolving (building a model). This update fixes that, and adds a test to build out the digital ocean tree as a model (which resolves thousands of deeply nested files).

Also a flatter report model was added for change detections. Instead of a tree of changes, a flat set of change slices is provided.

Addresses issues:

v0.15.11

16 Feb 14:49
Compare
Choose a tag to compare

Various fixes to the experience discovered when using vacuum through VSCode.

Addition of KeyNode to references, in order to extract the correct node value.