Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -178,6 +178,7 @@ The defaults are `off` or `warn` for `minimal` and `recommended` and `error` for
Also add the rule to the built-in rules list in [the config types tree](./packages/core/src/types/redocly-yaml.ts).

If the rule reflects a specification requirement, prefix it with `spec-` and add it to the [spec ruleset](./packages/core/src/config/spec.ts).
If a rule already exists for another specification flavor, reuse the existing name so the same concept stays discoverable across specs.

Separately, open a merge request with the corresponding documentation changes.
To make changes to documentation:
Expand Down
1 change: 1 addition & 0 deletions docs/@v2/commands/bundle.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ The `bundle` command pulls the relevant parts of an API description into a singl

The `bundle` command differs from the [`join`](./join.md) command.
The `bundle` command takes a root OpenAPI file as input and follows the `$ref` mentions to include all the referenced components into a single output file.
All components are automatically resolved and included without requiring explicit definitions.
The `join` command can combine multiple OpenAPI files into a single unified API description file.

The `bundle` command first executes preprocessors, then rules, then decorators.
Expand Down
Loading