-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
test: Fix types test #28
Conversation
tests/types/types.test.ts
Outdated
css satisfies ESLint.Plugin; | ||
// TODO: Uncomment when ESLint.Plugin can accept non-JS rules | ||
// css satisfies ESLint.Plugin; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this change is necessary. It looks like the type test is passing. We can always comment out the failing parts of the test in a PR if it's necessary to add a new rule. And I will have a look at eslint/eslint#19157 soon so we can get type support for non-JS rules in the main repo.
Another issue that I ran into with test is that we need to be sure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Just a suggestion to remove an unused comment, then LGTM.
Co-authored-by: Francesco Trotta <[email protected]>
Prerequisites checklist
What is the purpose of this pull request?
Fix the types test.
What changes did you make? (Give an overview)
Commented out the test to verify that the plugin satisfiesESLint.Plugin
. This can't happen becauseESLint.Plugin
rules aren't yet updated to match language plugin rules type.Ensure that
npm run build
is always run before the types test.Related Issues
Is there anything you'd like reviewers to focus on?