Support for extending a base configuration file

[oalfred]

I have been trying to use the extension setting

"ruff.configuration": ...

to point to a base configuration file that I could then override in a project specific pyproject.toml. Analogously to how the ruff setting "extend" works. But any settings I make in pyproject.toml are ignored, which leads me to believe that when "ruff.configuration" is used the extension does not also read the pyproject.toml. Could we have a setting that selects a base config but still allows project specific overrides?

Thank you for your work on this extension!

---

For completeness, I considered using

[tool.ruff]
extend = "/path/to/shared/config/ruff.toml"

in the pyproject.toml directly but I don't want a hard coded path and despite my best efforts I was not able to find a practical way to set an environment variable in vscode. I also tried using an inline configuration in the workspace settings file like so

"ruff.configuration": {
    "extend": "/path/to/shared/config/ruff.toml"
}

but the server told me Failed to load settings from `configuration`: using `extend` is unsupported for inline configuration.

[MichaReiser]

I'm not sure I follow. Can you share a more complete example:

• What's your VS code configuration
• What's the rough structure of your shared pyproject.toml
• What's the structure of the project specific pyproject.toml

What's the output you expect (e.g. a specific setting that should be set)

[oalfred]

Yes, of course, I will try give more details.

Let's say I have this in a shared config

[lint]
select = ["ANN"]

that is located in /path/to/shared/config/ruff.toml. And in a Python project (located somewhere else) I have this pyproject.toml:

[project]
name = "test-project"
version = "0.1.0"
requires-python = "~=3.12.11"

[tool.ruff]
extend = "/path/to/shared/config/ruff.toml"

Now, if I make a simple test file in that project that contains

def fun(a):
    print(a)

then Ruff will correctly point out that there is no return type annotation for the function (ANN201) and no type annotation for the parameter (ANN001). If I add ignore = ["ANN001"] in the Ruff section of the pyproject.toml that warning disappears but ANN201 remains. So far so good.

However, if I add this to my vscode workspace settings.json

"ruff.configuration": "/path/to/shared/config/ruff.toml"

and remove the extend from pyproject.toml so that we only have

[project]
name = "test-project"
version = "0.1.0"
requires-python = "~=3.12.11"

[tool.ruff]
ignore = ["ANN001"]

then Ruff again shows the ANN001 warning, i.e., the ignore in pyproject.toml no longer works.

What I would like is a setting similar to "ruff.configuration": "..." but that allows overrides in my project's pyproject.toml, just like how it works when I use extend.