🐛 Ignore monorepo settings

[jezikk]

Zed version

Zed: v0.191.7 (Zed) OS: macOS 15.5.0 Memory: 18 GiB Architecture: aarch64

Extension version

0.2.0

Biome version

2.0.5

Operating system

• Windows
• macOS
• Linux

Description

The extension doesn't respect monorepo settings. In subfolder it shows errors which should ignore according to settings from the parent biome.json file.

Project structure:

Parent biome.json:

{
	"$schema": "./node_modules/@biomejs/biome/configuration_schema.json",
	"root": true,
	"linter": {
		"enabled": true,
		"rules": {
			"recommended": true,
			"correctness": {
				"useExhaustiveDependencies": "warn"
			},
			"nursery": {
				"useUniqueElementIds": "off"
			}
		}
	},
	"assist": {
		"enabled": true,
		"actions": {
			"source": {
				"organizeImports": "on"
			}
		}
	},
	"formatter": {
		"enabled": true,
		"indentStyle": "tab",
		"indentWidth": 4
	},
	"vcs": {
		"enabled": true,
		"clientKind": "git",
		"useIgnoreFile": true
	}
}

Child biome.json:

{
  "$schema": "./node_modules/@biomejs/biome/configuration_schema.json",
  "root": false,
  "extends": "//",
  "files": {
    "includes": ["./app/**"]
  }
}

If I run linter from terminal it returns no errors, but in IDE it shows errors which is ignored in parent biome.json.

.zed/settings.json

{
	"lsp": {
		"biome": {
			"settings": {
				"config_path": "./organizer-dashboard/biome.json"
			}
		}
	},
	"languages": {
		"JavaScript": { "formatter": { "language_server": { "name": "biome" } } },
		"TypeScript": { "formatter": { "language_server": { "name": "biome" } } },
		"JSX": { "formatter": { "language_server": { "name": "biome" } } },
		"TSX": { "formatter": { "language_server": { "name": "biome" } } },
		"JSON": { "formatter": { "language_server": { "name": "biome" } } },
		"JSONC": { "formatter": { "language_server": { "name": "biome" } } },
		"CSS": { "formatter": { "language_server": { "name": "biome" } } }
	}
}

Steps to reproduce

You should reproduce the monorepo project structure.

Expected behavior

Logic in IDE is inlined with linter using terminal.

Does this issue occur when using the CLI directly?

No

Link to a minimal reproduction

No response

[ematipico]

Does Biome work if you remove the custom configuration path?

[jezikk]

Global config:

 "biome": {
      "settings": {
        "require_config_file": true
      }
    }

.zed/settings.json

{
	"languages": {
		"JavaScript": { "formatter": { "language_server": { "name": "biome" } } },
		"TypeScript": { "formatter": { "language_server": { "name": "biome" } } },
		"JSX": { "formatter": { "language_server": { "name": "biome" } } },
		"TSX": { "formatter": { "language_server": { "name": "biome" } } },
		"JSON": { "formatter": { "language_server": { "name": "biome" } } },
		"JSONC": { "formatter": { "language_server": { "name": "biome" } } },
		"CSS": { "formatter": { "language_server": { "name": "biome" } } }
	}
}

Still the same error. It is a monorepo where the root biome.json file is not placed in the project root

[ematipico]

Thank you. We usually recommend to place the root configuration at the root of the project.

I'll see if your case is a setting we're able to support. In the meantime:

• you can place the root configuration at the root
• provide us with a reproduction, a repository, so we can debug it and reproduce the issue

[github-actions]

Hello @jezikk, please provide a minimal reproduction. You can use one of the following options:

• Provide a link to our playground, if it's applicable.
• Provide a link to GitHub repository. To easily create a reproduction, you can use our interactive CLI via npm create @biomejs/biome-reproduction

Issues marked with S-Needs repro will be closed if they have no activity within 3 days.

[jezikk]

There is a repo for reproduction: https://github.com/jezikk/biome-microservices

Page with linter error is there:

I know that our use case is not standard, because we have independent services with different technology stack in one repository.

[ematipico]

Ok, I think it should work with the config path setting, and I believe that's the bug we want to fix.

I think the current production lacks this setting.

Thanks for the report

[KhoaLee]

@ematipico Sorry I have to put this here cause I have posted another comment in biome repo. I have the issue which kind of similar to @jezikk. You can look here: biomejs/biome#6483 (comment).

I am wonder if this is related to this issue. Thanks.