Reviewing files that changed from the base of the PR and betweenef04b8d andd5eecf0.

• .coderabbit.yaml (1 hunks)
• .oxlintrc.json (1 hunks)
• oxc1.js (1 hunks)
• oxc1.test (1 hunks)
• oxc3.test (1 hunks)
• oxc5.js (1 hunks)

.oxlintrc.json (1)

1-5:Aggressive rule configuration suitable for testing purposes.

The configuration sets all oxlint rules to error severity, which is appropriate for this PR's purpose of demonstrating linting capabilities with intentionally problematic code. However, be aware that this configuration would be too strict for typical production use, where you'd want to selectively enable rules or set some to "warn" level.

.coderabbit.yaml (1)

1-7:Configuration correctly enables oxc testing.

The configuration appropriately enables oxc linting while disabling biome, and the path_filters ensure all files are included for review. This aligns well with the PR's objective of testing oxlint capabilities.

oxc1.js (1)

1-36:Intentional error catalog for linting validation.

This file serves as a collection of deliberately invalid JavaScript patterns to test oxlint's error detection capabilities. Each snippet is properly labeled with its error type (redeclared variables, duplicate parameters, constant reassignment, etc.). This is appropriate for a testing/demonstration repository.

oxc5.js (1)

1-42:Intentional anti-patterns for code quality demonstration.

This file contains deliberately poor coding practices and code smells (unused variables, loose equality, debugger statements, deep nesting, etc.) to demonstrate oxlint's code quality checks. Each issue is properly commented. This is appropriate for testing and validation purposes.

oxc3.test (1)

1-107:Comprehensive TypeScript error catalog for validation.

This test file provides an extensive collection of intentionally invalid TypeScript constructs covering type errors, redeclarations, control flow issues, scope problems, enum/interface concerns, and async/sync misuse. The variety and coverage make it valuable for validating oxlint's TypeScript error detection capabilities.

oxc1.test (1)

1-68:Good comprehensive coverage of common linting violations.

The test file successfully demonstrates a wide range of linting issues including unused variables, unreachable code, missing semicolons, redeclarations, non-strict equality, empty blocks, console statements, variable shadowing, var usage, indentation issues, trailing spaces, mixed tabs/spaces, and undefined variables.