Update documentation to mention `etcetera` crate instead of `dirs` for user configuration discovery (#12064)

This commit is contained in:
Micha Reiser 2024-06-27 10:50:09 +02:00
parent 22cebdf29b
commit 0917ce16f4
1 changed files with 2 additions and 2 deletions

View File

@ -270,8 +270,8 @@ There are a few exceptions to these rules:
1. If no config file is found in the filesystem hierarchy, Ruff will fall back to using 1. If no config file is found in the filesystem hierarchy, Ruff will fall back to using
a default configuration. If a user-specific configuration file exists a default configuration. If a user-specific configuration file exists
at `${config_dir}/ruff/pyproject.toml`, that file will be used instead of the default at `${config_dir}/ruff/pyproject.toml`, that file will be used instead of the default
configuration, with `${config_dir}` being determined via the [`dirs`](https://docs.rs/dirs/4.0.0/dirs/fn.config_dir.html) configuration, with `${config_dir}` being determined via [`etcetera`'s native strategy](https://docs.rs/etcetera/latest/etcetera/#native-strategy),
crate, and all relative paths being again resolved relative to the _current working directory_. and all relative paths being again resolved relative to the _current working directory_.
1. Any config-file-supported settings that are provided on the command-line (e.g., via 1. Any config-file-supported settings that are provided on the command-line (e.g., via
`--select`) will override the settings in _every_ resolved configuration file. `--select`) will override the settings in _every_ resolved configuration file.