spectral
spectral copied to clipboard
A flexible JSON/YAML linter for creating automated style guides, with baked in support for OpenAPI v3.1, v3.0, and v2.0 as well as AsyncAPI v2.x.
**Describe the bug** We use a ruleset that extends **oas** ruleset. We have a document with a **$ref** in it. When we `run` spectral, the `source` in the result set...
**User story.** As a spectral user, i should be able to use aliases from an extended ruleset within a ruleset i'm authoring. **Is your feature request related to a problem?**...
Some rebase went wrong and my previous attempt at doing this (https://github.com/stoplightio/spectral/commit/3ad596b52e75f90c00bfb961350f6096f9a902a0) fell into the void.
**Chore summary** We have the [`aliases` feature](https://meta.stoplight.io/docs/spectral/e5b9616d6d50c-custom-rulesets#aliases) to help users target certain parts of a spec without having to remember the JSONPath expression, and we have 2 already created [here](https://github.com/stoplightio/spectral/blob/4447d81ace5aab90e7cd48a8e182103b6a90ee81/packages/rulesets/src/oas/index.ts#L32-L38)...
**User story.** As a developer, I want to write `AsyncAPI` rules working on the *"effective"* AsyncAPI document. *Effective* meaning that [Operation](https://www.asyncapi.com/docs/reference/specification/v2.4.0#operationObject), and [Message](https://www.asyncapi.com/docs/reference/specification/v2.4.0#messageTraitObject) traits (see fields) have been applied to...
@philsturgeon related to this [other PR](https://github.com/stoplightio/spectral/pull/2187#discussion_r938855924), I took a pass at making it clearer in the README that the user needs to create a local ruleset to run `lint` without...
**Chore summary** Update our docs with working examples for writing JS/TS rulesets. **Additional context** - https://github.com/stoplightio/spectral/issues/2107#issuecomment-1207173671 - https://apisyouwonthate.com/blog/distribute-spectral-style-guides-with-npm#publish-your-spectral-style-guide-to-npm
**User story.** As a developer, I can use `js` modules rulesets with mixed exports (named and default), so that I can improve my development experience. **Is your feature request related...
**Describe the bug** A clear and concise description of what the bug is. **To Reproduce** 1. Given this ruleset file ``` > cat myruleset.js import { oas2, oas3 } from...
**Chore summary** Take a pass at reorganizing the rulesets and custom rulesets into its own section, and breakdown information into separate pages. The custom ruleset page specifically has a lot...