Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

linter: no matching rules for some typescript rules #7233

Closed
Boshen opened this issue Nov 11, 2024 · 0 comments · Fixed by #7622
Closed

linter: no matching rules for some typescript rules #7233

Boshen opened this issue Nov 11, 2024 · 0 comments · Fixed by #7622
Assignees
Labels
A-linter Area - Linter

Comments

@Boshen
Copy link
Member

Boshen commented Nov 11, 2024

          Hi team, I ran oxlint and I caught some issues:
! The following rules do not match the currently supported rules:
  | typescript/no-dupe-class-members
  | typescript/no-useless-constructor
  | typescript/no-loss-of-precision
  | typescript/no-array-constructor
  | typescript/no-redeclare
  | typescript/no-unused-vars

But, you can see all these rules have been implemented. I am using "oxlint": "^0.11.0",

Originally posted by @markEHVN in #2180 (comment)

@camchenry camchenry added the A-linter Area - Linter label Nov 12, 2024
Boshen pushed a commit that referenced this issue Nov 13, 2024
- related to #6988

This is causing a lot of errors currently such as
#7233. I think we need to
handle rule names more robustly first:

- #7240
- #7082
- #7242

then, I think we can revisit this and maybe implement it as an actual
lint plugin too? #7086
Dunqing pushed a commit that referenced this issue Nov 17, 2024
- related to #6988

This is causing a lot of errors currently such as
#7233. I think we need to
handle rule names more robustly first:

- #7240
- #7082
- #7242

then, I think we can revisit this and maybe implement it as an actual
lint plugin too? #7086
Dunqing pushed a commit that referenced this issue Nov 18, 2024
- related to #6988

This is causing a lot of errors currently such as
#7233. I think we need to
handle rule names more robustly first:

- #7240
- #7082
- #7242

then, I think we can revisit this and maybe implement it as an actual
lint plugin too? #7086
Dunqing pushed a commit that referenced this issue Nov 18, 2024
- related to #6988

This is causing a lot of errors currently such as
#7233. I think we need to
handle rule names more robustly first:

- #7240
- #7082
- #7242

then, I think we can revisit this and maybe implement it as an actual
lint plugin too? #7086
@Boshen Boshen self-assigned this Nov 21, 2024
@Sysix Sysix assigned Sysix and unassigned Boshen Dec 3, 2024
@Boshen Boshen closed this as completed in 29db060 Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linter Area - Linter
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants