Skip to content
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

feat: api rewrite & community release #66

Merged
merged 89 commits into from
Dec 11, 2018
Merged

feat: api rewrite & community release #66

merged 89 commits into from
Dec 11, 2018

Conversation

marbemac
Copy link
Contributor

BREAKING CHANGE: api-rewrite, prepare external release

tbarn and others added 30 commits October 30, 2018 15:45
SL-786
- deep cloning the provided rulset
SL-787

BREAKING CHANGE: rule's name changed.
Was: a  simple {name}
Is: "{format}-{name}"
SL-787

That could never possibly happen.
Paths are derived directly from rule.path
…-ruleset-should-not-change

SL-786 fix: prevent ruleset to be mutated
…ge-tool

[SO-15] build: add code coverage reporting and codeclimate
…rrect-description

fix: typo in api-host rule description
SL-787

most changes happened in index.ts
- split up `run` code into composable chunks
- got rid of iterating through `paths` (works exactly the same now)
SL-787

- it didn't assure uniqueness and was redundant
…ifferent-formats

SL-787: same rules under different formats
Chris Miaskowski and others added 27 commits December 10, 2018 23:53
SO-23
- setFunctions/updateFunctions
- setRules/updateRules
SO-23
- remove Spectral constructor
- remove update/set rules functions
SO-23
BREAKING CHANGES
SO-23
BREAKING CHANGE
SO-23
Breaking Change
many use cases don’t need it
still need to test tons of rules…
@marbemac marbemac merged commit 77d033f into master Dec 11, 2018
@marbemac
Copy link
Contributor Author

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants