-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(eslint-plugin): [no-unsafe-assignment] be more specific about error types #8304
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(eslint-plugin): [no-unsafe-assignment] be more specific about error types #8304
Conversation
Thanks for the PR, @tobySolutions! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
A great start, thanks again for working on this with me!
Requesting changes mostly around adding in more testing. A couple small refactors too. But the functionality looks great! ✨
👋 @tobySolutions ping, just checking in - is this something you still have the time and energy for? It's still in draft & there are some CI ❌s so we haven't looked at it. |
Definitely Josh! I will resume work on this in a bit. Thank you so very much for checking in! 🙌 |
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.
Progress! 🚀
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.
🙌 Great! Thanks for working with me on this @tobySolutions. I'm excited to see a better error message for no-unsafe-assignment
on production soon!
Only one change request left from me, to add a bit more to the tests. It's a pretty small thing - so marking as 1 approval
to let someone else from the team chime in if the want.
packages/eslint-plugin/tests/rules/no-unsafe-assignment.test.ts
Outdated
Show resolved
Hide resolved
Yay!!! |
If it only changes one rule, then it doesn't fix #8231, only partially |
Yup - I'm about to post an edit splitting the issue up 😄 |
What about other |
🙌 Filed! |
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.
This is wonderful, thanks @tobySolutions!
We've got a bunch of issues filed to apply similar improvements to other no-unsafe-*
rules. I think once we've gone through those we'll be well-positioned to review our messaging around "error" types and maybe iterate further on how they're explained to users. But that's a battle for another day.
293fb24
into
typescript-eslint:main
Thank you so much for being super awesome Josh!!! This was such an amazing experience. I look forward to more contributions |
We'll also need a |
PR Checklist
Overview