From 88e1a4bcdee1d3d0126fb862bfb127af94f1f757 Mon Sep 17 00:00:00 2001 From: Phil Sturgeon <67381+philsturgeon@users.noreply.github.com> Date: Mon, 30 May 2022 13:19:41 +0100 Subject: [PATCH] docs(repo): link to JetBrains integration (#2161) --- README.md | 7 ++++--- docs/guides/4-custom-rulesets.md | 2 +- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index e0186b94b..f73e3a490 100644 --- a/README.md +++ b/README.md @@ -91,9 +91,10 @@ No problem! A hosted version of Spectral comes **free** with the Stoplight platf ## ⚙️ Integrations -- [Stoplight Studio](https://stoplight.io/studio?utm_source=github&utm_medium=spectral&utm_campaign=readme) uses Spectral to validate and lint OpenAPI documents. -- [Spectral GitHub Action](https://github.com/stoplightio/spectral-action), lints documents in your repo, built by [Vincenzo Chianese](https://github.com/XVincentX/). -- [VS Code Spectral](https://github.com/stoplightio/vscode-spectral), all the power of Spectral without leaving VS Code. +- [GitHub Action](https://github.com/stoplightio/spectral-action) - lints documents in your repo, built by [Vincenzo Chianese](https://github.com/XVincentX/). +- [Jetbrains Plugin](https://plugins.jetbrains.com/plugin/18520-spectral), Automatic linting of your OpenAPI specifications and highlighting in your editor. +- [Stoplight Studio](https://stoplight.io/studio?utm_source=github&utm_medium=spectral&utm_campaign=readme) - Uses Spectral to validate and lint OpenAPI documents. +- [VS Code Spectral](https://marketplace.visualstudio.com/items?itemName=stoplight.spectral), all the power of Spectral without leaving VS Code. ## 🏁 Help Others Utilize Spectral diff --git a/docs/guides/4-custom-rulesets.md b/docs/guides/4-custom-rulesets.md index 0bb994b77..7f071e34f 100644 --- a/docs/guides/4-custom-rulesets.md +++ b/docs/guides/4-custom-rulesets.md @@ -50,7 +50,7 @@ where you may need to run a rule on the "raw" un-resolved document. For example, if you want to enforce conventions on the folder structure used for [splitting up -documents](https://stoplight.io/blog/keeping-openapi-dry-and-portable/?utm_source=github&utm_medium=spectral&utm_campaign=docs). +documents](https://blog.stoplight.io/keeping-openapi-dry-and-portable?utm_medium=spectral&utm_source=github&utm_campaign=docs). If your rule needs to access the raw `$ref` reference values, you can set `resolved: false` to allow the rule to receive the raw un-resolved version of