Releases: wework/speccy
Releases · wework/speccy
v0.8.0
Changed
- Switched to using oas-kit for resolving and validating
- Moved
short-summary
fromwework
tostrict
rules (#110) - YAML files were previously loaded in "JSON mode", which meant duplicate keys were allowed. They will now error (#108)
Added
- Config files can be passed with
-c
(defaults tospeccy.yaml
). See README for more information - Enabled
path-keys-no-trailing-slash
now oas-resolver can handle keys for lint rules - Enabled better-ajv-errors for beautiful validation errors. Linter errors remain unchanged
Fixed
- Resolving to a file would silently fail when writing to a folder that did not exist
Removed
- Got rid of
wework
rules, as the last rule was moved tostrict
(#110)
v0.7.3
v0.7.2
v0.7.0
Breaking Change
- Error now raised for all commands when
$ref
points to a file that does not exist, or cannot be opened
Fixed
- Bumped
json-schema-to-openapi-schema
to v0.2.0 so subschemas will be converted - Invalid keywords will be stripped everywhere instead of just root
v0.6.0
0.5.4
Changed
properties
rule will now ignore extensions, sofoo: 'a', x-bar: 'b'
is only 1 property.
Fixed
- Disabled
reference-components-regex
rule until resolver can allow it to work. Re-enabling this rule is being tracked in #43
Note
This release hoped to solve the overly verbose errors, where the entire object is flung into the CLI output. It's a known issue, and has been partially improved in #40, but more work needs to be done.