Skip to content

docs: explicitly describe that the migrate command automatically migrate linters.presets #5697

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Apr 5, 2025
Merged

docs: explicitly describe that the migrate command automatically migrate linters.presets #5697

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
500d985
docs: explicitly specify that the migrate command writes individual l…
kyu08 Apr 5, 2025
ecf6c02
review
ldez Apr 5, 2025
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
6 changes: 5 additions & 1 deletion docs/src/docs/product/migration-guide.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,8 @@ The `migrate` command enforces the following default values:

Other fields explicitly defined in the configuration file are migrated even if the value is the same as the default value.

The `migrate` command automatically migrates `linters.presets` in individual linters to `linters.enable`.

```txt
Migrate configuration file from v1 to v2

Expand Down Expand Up @@ -189,7 +191,9 @@ There are 2 new options (they are not strictly equivalent to the previous option

#### `linters.presets`

This property have been removed.
This property has been removed.

The `migrate` command automatically migrates `linters.presets` in individual linters to `linters.enable`.

<details>
<summary style={{color: '#737380', paddingLeft: '1rem'}}>v1</summary>
Expand Down
Loading