API versioning can be a scary topic but there are a few easy wins that are always best avoided when using OpenAPI to describe an API, like not squashing multiple global versions into a single file.
npm install --save -D @stoplight/spectral-url-versioning
npm install --save -D @stoplight/spectral-cliCreate a local ruleset that extends the ruleset. In its most basic form this just tells Spectral what ruleset you want to use, but it will allow you to customise things, add your own rules, turn bits off if its causing trouble.
cd ~/src/<your-api>
echo 'extends: ["@stoplight/spectral-url-versioning"]' > .spectral.yaml
If you're using VS Code or Stoplight Studio then the NPM modules will not be available. Instead you can use the CDN hosted version:
echo 'extends: ["https://unpkg.com/@stoplight/spectral-url-versioning/dist/ruleset.mjs"]' > .spectral.yaml
Note: You need to use the full URL with CDN hosted rulesets because Spectral cannot follow redirects through extends.
Next, use Spectral CLI to lint against your OpenAPI description. Don't have any OpenAPI? Record some HTTP traffic to make OpenAPI and then you can switch to API Design-First going forwards.
spectral lint api/openapi.yaml
You should see some output like this:
/Users/phil/src/protect-earth-api/api/openapi.yaml
44:17 warning no-path-versioning #/paths/~1v1 contains a version number. API paths SHOULD NOT have versioning in the path. It SHOULD be in the server URL instead. paths./v1
Now you have some things to work on for your API. Thankfully these are only at the warning severity, and that is not going to fail continuous integration (unless you want them to).
There are a bunch of other rulesets you can use, or use for inspiration for your own rulesets and API Style Guides.
- Phil Sturgeon - Made some of these fairly opinionated but probably reasonable rules.
This repository is licensed under the MIT license.
If you would like to thank us for creating Spectral, we ask that you buy the world a tree.