🐛 overrides overrides extends overrides 😂

[unional]

Environment information

CLI:
  Version:                      1.7.2
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.10.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/9.0.6"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?

// biome.json
{
  "extends": ["./some-config.json"],
  "overrides": [{...}]
}

/// some-config.json
{
  "overrides": [{...}, { "include": ["package.json"], "formatter": { "lineWidth": 20 } }]
}

The overrides in biome.json overrides overrides in some-config.json

specifically, I observe the package.json override does not work until I do:

// biome.json
{
  "extends": ["./some-config.json"],
  "overrides": [{...}, { "include": ["package.json"], "formatter": { "lineWidth": 20 } }]
}

Expected result

The overrides in biome.json concatenates overrides in some-config.json

Code of Conduct

• I agree to follow Biome's Code of Conduct

[Conaclos]

Instead of replacing the inherited overrides, we could extend it by first copying it and the appending the new overrodes. This is technically a breaking change. This could be changed in Biome 2.0

[ematipico]

I'm not really sure about this...

Using extends inside overrides was one of the reasons why eslint pushed for a flat config.

Our configuration is already complex, and we should weigh more complexity very carefully and justify it very well.

I am going to close this issue for now because I prefer to not push more complexity on the configuration as a bug fix. As mentioned by Vic, it's a possible breaking change.

I will move this issue into a discussion.