Skip to content

linter: expose JS objects with categories, plugins and rule names #19486

Description

@camc314

I'm imagining a more generic solution to 19482.

The rough idea is that we would export some data like:

type PluginName =  "eslint" | "oxc" | "typescript" | "jest" | "vitest"...;
type Category = "correctness" | "restriction" | ...;

export declare const allRules: {
    plugin: PluginName
    rule: string
    category: Category;
}[]

This way, through dynamic configs, users can manipulate the rule set, categories ect into the shape they want through standard JS.

This data would be codegen-ed.

Refs: #19482

Metadata

Metadata

Assignees

Labels

A-linterArea - LinterC-enhancementCategory - New feature or request

Fields

Priority

None yet

Start date

None yet

Target date

None yet

Effort

None yet

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions