-
Notifications
You must be signed in to change notification settings - Fork 236
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
fix: update @typescript-eslint/experimental-utils
to v5
#941
Conversation
@@ -681,7 +681,7 @@ const isTestCaseName = (node: TSESTree.LeftHandSideExpression) => | |||
TestCaseName.hasOwnProperty(node.name); | |||
|
|||
const isTestCaseProperty = ( | |||
node: TSESTree.Expression, | |||
node: TSESTree.Expression | TSESTree.PrivateIdentifier, |
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.
not sure if this is correct, but seems safe enough? 😀
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.
hahah yeah I think it should be fine just technically incorrect/nonsensical as a private identifier will never be what we want; but if CI is happy let's ship it 🎉
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.
tbh actually thinking about it probably is actually fine because if we're got a node that could be one of those types, it'll be nicer on our rules to handle it here rather than having to check in each rule before calling this method 🤷
@@ -681,7 +681,7 @@ const isTestCaseName = (node: TSESTree.LeftHandSideExpression) => | |||
TestCaseName.hasOwnProperty(node.name); | |||
|
|||
const isTestCaseProperty = ( | |||
node: TSESTree.Expression, | |||
node: TSESTree.Expression | TSESTree.PrivateIdentifier, |
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.
hahah yeah I think it should be fine just technically incorrect/nonsensical as a private identifier will never be what we want; but if CI is happy let's ship it 🎉
## [25.0.4](v25.0.3...v25.0.4) (2021-10-11) ### Bug Fixes * update `@typescript-eslint/experimental-utils` to v5 ([#941](#941)) ([afad49a](afad49a))
🎉 This PR is included in version 25.0.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This should enable compat with
eslint@8
even if we can't test against it (thus add it topeerDependencies
) yet