Open
Description
What problem do you want to solve?
Coming over from eslint/eslint#19431 (comment): the playground on http://eslint.org/play right now does not support TypeScript syntax. Now that rules are adding support for TS syntax (eslint/eslint#19173), this blocks their TS-specific blocks from being represented in the playground.
What do you think is the correct solution?
How about:
- Adding an opt-in option to use
@typescript-eslint/parser
- Having rule samples that use a TypeScript language enable that option
Participation
- I am willing to submit a pull request for this change.
Additional comments
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Implementing
Activity
nzakas commentedon Mar 17, 2025
This seems like a good idea. We'd probably want that option under "Versioning and Config". Would we need any other options for TypeScript parsing?
default-param-last
eslint/eslint#19431JoshuaKGoldberg commentedon Mar 17, 2025
TypeScript would need to know:
<div>
that might be an assertion or a JSX elementBoth of those are already in "Versioning and Config".
nzakas commentedon Mar 17, 2025
Awesome, thanks for the clarification.
Tanujkanti4441 commentedon Mar 18, 2025
I'll take this.
TypeScript
parser support to playground #714