v0.15.12

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:

• daveshanley/vacuum#459
• daveshanley/vacuum#460

v0.15.11

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

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

v0.15.10

Upgrades the timeout of a reference lookup in a node tree from 100 ms to 500. Reports of timeouts in the wild with systems under load, means this is triggered too often when it should not.

No new features, no other changes.

v0.15.9

Fixes some lookup issues reported by vacuum users. rolodex was getting a little confused with deeply nested lookups. This closes that gap and also closes off a TODO that was a known issue.

No new features.

v0.15.8

Resolution for #248

A new codepath created a double dip into the index, which skews the working path. A short circuit is required, and a new block of code catches it.

v0.15.7

In this release a new ParentNode property is captured by references and indexing errors. This makes it easier to visualize the root of a problem when using vacuum.

No other new features.

v0.15.6

Bugfix release

Addresses issues

• #160
• daveshanley/vacuum#390
• #159

Addresses a locking issue with the remote file loader discovered online, hopefully this should be the last instance of it.

v0.15.5

Bugfix release, no new features, no breaking changes.

Addresses issues:

• #243
• #240

An issue discovered where the rolodex was running away and locking cores (locked our 32vpcu instance).

v0.15.4

Fixed issue with invalid polymorphic circular reference tracking.

No new features.

v0.15.3

Adds a new property ContainsEmptyRequirement to SecurityRequirement objects. This is set to true if an empty security requirement is provided, which acts as a null / empty value. This is used downstream by applications looking at the security of a spec and matching it against a spec.

Also added better handling to the mock generator. Now it operates through the following stages:

Examples > Example > Generate data

The Preferred header can now extract the index of Examples in a schema.

Also cleans up some behavior for the bundler module

@Domarx