ruff server reads from a configuration TOML file in the user configuration directory if no local configuration exists

[snowsignal]

Summary

Fixes #11158.

A settings file in the ruff user configuration directory will be used as a configuration fallback, if it exists.

Test Plan

Create a pyproject.toml or ruff.toml configuration file in the ruff user configuration directory.

• On Linux, that will be $XDG_CONFIG_HOME/ruff/ or $HOME/.config
• On macOS, that will be $HOME/Library/Application Support
• On Windows, that will be {FOLDERID_LocalAppData}

Then, open a file inside of a workspace with no configuration. The settings in the user configuration file should be used.

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

[akthe-at]

Summary

Fixes #11158.

A settings file in the ruff user configuration directory will be used as a configuration fallback, if it exists.

Test Plan

Create a pyproject.toml or ruff.toml configuration file in the ruff user configuration directory.

• On Linux, that will be $XDG_CONFIG_HOME/ruff/ or $HOME/.config
• On macOS, that will be $HOME/Library/Application Support
• On Windows, that will be {FOLDERID_LocalAppData}

Then, open a file inside of a workspace with no configuration. The settings in the user configuration file should be used.

I could be reading this wrong but wouldn't the windows directory listed above end up being something like "%USERPROFILE%\AppData\Local" ? The current global config for ruff if not local is looked for in "${config_dir}/ruff/pyproject.toml" correct? Is it by design/desired to have these be different toml files or are they meant/able to live together in the same config toml file?

[charliermarsh]

The logic here is the same as elsewhere in Ruff -- it'll look in the same place.

[MichaReiser]

I expected more changes. This makes it look extremely easy 😆