-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
chore(lint): re-enable @typescript-eslint/ban-types
#3464
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
0c1a229
to
379897f
Compare
@typescript-eslint/ban-types
@typescript-eslint/ban-types
@typescript-eslint/ban-types
@typescript-eslint/ban-types
@typescript-eslint/ban-types
@typescript-eslint/ban-types
@typescript-eslint/ban-types
@typescript-eslint/ban-types
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.
looks good! had some concerns about if this would affect what TypeScript shows in the tooltip when you hover over a variable (the string representation of a type) but that seems to still be fine
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.
Lovely, thank you for taking action on this! It's looking great.
Just left a few comments inline where files that you might be able to undo the eslint-disable
s in.
@@ -1,3 +1,5 @@ | |||
/* eslint-disable @typescript-eslint/ban-types */ |
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.
Any particular reason for this one? I tried switching the {}
s to object
s in it and didn't see any build failures.
@@ -1,3 +1,5 @@ | |||
/* eslint-disable @typescript-eslint/ban-types */ |
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.
Any particular reason for this one? I tried switching the {}
to object
in it and didn't see any build failures.
@@ -1,3 +1,5 @@ | |||
/* eslint-disable @typescript-eslint/ban-types */ |
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.
Any particular reason for this one? I tried switching the {}
s to object
s in it and didn't see any build failures.
Context / Background: https://twitter.com/JoshuaKGoldberg/status/1606070961182228481
🎯 Changes
@typescript-eslint/ban-types
eslint-ignore
on any interop files✅ Checklist