🐛 Disabling a nursery rule, disable all nursery rules when global all is set.

[Conaclos]

Environment information

CLI:
  Version:                      12.1.3-nightly.50eb45f
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  ROME_LOG_DIR:                 unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.3.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/8.19.2"

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

Workspace:
  Open Documents:               0

Discovering running Rome servers...

What happened?

Given the following configuration:

{
  "linter": { "rules": {
      "all": true,
      "nursery": { "noConfusingArrow": "off" }
    }
} }

or even simpler:

{
  "linter": { "rules": {
      "all": true,
      "nursery": { }
    }
} }

The following code doesn't trigger useNamingConvention

export function TEST() {}

While the following config did:

{
  "linter": { "rules": {
      "all": true
    }
} }

I think it is an unintended effect from #4511.

Expected result

All nursery rules should be enabled (except the ones turned off).

Code of Conduct

• I agree to follow Rome's Code of Conduct