-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v0.9.0 #262
Release v0.9.0 #262
Conversation
06fbdb5
to
0ab2c3f
Compare
@philsturgeon JSON is a subset of YAML, so you can still write (and read) rulesets in JSON, making it not a breaking change. |
Ahh yeah, and seeing as the extension is not enforced it doesn't matter! I'll update, thank you. |
|
||
<hr> | ||
|
||
### Creating Rule Actions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MikeRalphson do you have docs for creating rule actions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean like a CONTRIBUTING.md
or a section in https://github.com/Mermade/oas-kit/blob/master/docs/linter-rules.md? Hmm, not yet, but it's a good idea, so I've opened a tracking issue Mermade/oas-kit#144
861752f
to
a2c91c7
Compare
The mega PR #248 changed so much it deserves its own release. The development version v0.9.0-1 has already been tagged for testing, and seems to be working.
Breaking
lib/linter.js
module has been entirely removed, and oas-linter is now used directly (#248)Fixed
application/vnd.api+json
) are now encoded correctly (#248)--skip
and the matching config option are no longer being ignored