Skip to content

oxlint/lsp: root config not applied if nested workspace folders are active #19061

Description

@asbrum

What version of Oxlint are you using?

extension version 1.4.3

What command did you run?

No response

What does your .oxlintrc.json config file look like?

no config

What happened?

Hi there,

if a repo has workspace settings, and folders configured, the extension is broken.

Small sample workspace settings

// vs code workspace settings
{
    "folders": [
        {
            "name": "root",
            "path": "."
        },
        {
            "name": "app1",
            "path": "apps/app1"
        },
        {
            "name": "app2",
            "path": "apps/app2"
        },
        {
            "name": "libs",
            "path": "libs"
        }
    ],
	// ...
}

The LSP tries to load a config for each of the folders, not only for root.
I tried disableNestedConfig too, but it doesn't work either.

In a large monorepo the folder settings are a common approach.

Metadata

Metadata

Assignees

Labels

A-editorArea - Editor and Language ServerA-linterArea - Linter

Type

Fields

Priority

None yet

Effort

None yet

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions