We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@eslint/compat
@eslint/config-array
@eslint/migrate-config
@eslint/object-schema
We have several packages that have at least one .ts file, but we have no automation aside from running tsc to check its validity.
.ts
tsc
We should set up typescript-eslint to lint all .ts files. This will double as an integration test for us with typescript-eslint.
@JoshuaKGoldberg feel like taking this one?
The text was updated successfully, but these errors were encountered:
I'd love to. 🙂
Sorry, something went wrong.
I think I should wait until #68 is in.
JoshuaKGoldberg
Successfully merging a pull request may close this issue.
Which packages would you like to change?
@eslint/compat
@eslint/config-array
@eslint/migrate-config
@eslint/object-schema
What problem do you want to solve?
We have several packages that have at least one
.ts
file, but we have no automation aside from runningtsc
to check its validity.What do you think is the correct solution?
We should set up typescript-eslint to lint all
.ts
files. This will double as an integration test for us with typescript-eslint.Participation
Additional comments
@JoshuaKGoldberg feel like taking this one?
The text was updated successfully, but these errors were encountered: