[romankurakin]

OXC.Lint.run/2 forwards category names to tsgolint as individual rules. This prevents callers from using the same category-based configuration for syntax and type-aware checks.

Resolve categories through the bundled native rule registry before invoking tsgolint. Select rules from enabled plugins and preserve explicit rule options and severities. Apply all first, then categories, then individual rules, so explicit exclusions take precedence.

The existing OXC.Lint.run/2 interface remains unchanged. For example, rules: %{"correctness" => :deny} now selects type-aware correctness rules without requiring callers to list them individually.

Closes #6.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[dannote]

Thanks, this is the right fix. I rebased it onto 0.18 and pushed to your branch; your commit keeps you as the author.

Changes from the original, to match 0.18's typed lint interface:

• build_lint_config sorts filters (all, then categories, then rules) by their parsed LintFilterKind, so the ordering fix covers syntax linting without a category list on the Elixir side.
• type_aware_rules takes and returns RuleSeverity values, and selects rules only when all or a category filter is present. That keeps the current behavior for configs that name rules individually.
• Named typescript/* rules keep their options and still reach tsgolint when oxlint doesn't know them. There's a test for this.
• The tests use 0.18's string plugin names and :error/:warning severities.