💅 useNamingConvention: allow consecutive capitals on generic parameters

[kevinwolfcr]

Environment information

CLI:
  Version:                      1.7.3
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

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

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

Linter:
  Recommended:                  false
  All:                          true
  Rules:                        nursery/useSortedClasses = {"level":"error","options":{"attributes":["class","className","className","classList"],"functions":["clsx","cva","tw","cn"]}}

Workspace:
  Open Documents:               0

Rule name

useNamingConvention

Playground link

https://biomejs.dev/playground/?lintRules=all&code=ZgB1AG4AYwB0AGkAbwBuACAAdABlAHMAdAA8AFQAQQByAGcAPgAoAGEAcgBnADoAIABUAEEAcgBnACkAIAB7AAoAIAAgAHIAZQB0AHUAcgBuACAAYQByAGcACgB9AAoACgB0AGUAcwB0ACgAMQApAA%3D%3D

Expected result

It should not report consecutive capitals on generic parameters, since a lot of people likes using T{GenericName}.

Code of Conduct

• I agree to follow Biome's Code of Conduct

[Conaclos]

You can disable the strictCase option?
We are also working on implementing custom convention in #2770