-
-
Notifications
You must be signed in to change notification settings - Fork 33
FYI: typescript-eslint@v6 will remove parserServices.hasFullTypeInformation #678
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
Comments
Hi, Could it be caused by this change? |
v6 isn't supported yet. I'll should be able to work on this sometime in the next week. |
Many thanks. Can I help? :) |
@pegak Thanks for the offer, but I should be good. I've already done the majority of the work back when v6 was in beta. I just need to finish it. I'm starting back on it now. |
6.0.0-next.1 is now available for testing. |
🎉 This issue has been resolved in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
👋 Hi! I'm one of the maintainers of typescript-eslint. We're getting ready to release a new v6 major version of the tooling, which includes some small breaking changes.
Coming over from typescript-eslint/typescript-eslint#7124: I see this repo contains references to
hasFullTypeInformation
. That property is something we've never recommended using (see that issue & typescript-eslint/typescript-eslint#7158). We recommend instead usingESLintUtils.getParserServices
per https://typescript-eslint.io/developers/custom-rules#typed-rules.If you really want to "progressively enhance" lint rules,
parserServices.program
will benull
if type information isn't available. But we definitely recommend against that kind of rule behavior changing.Overall, I'd suggest trying out typescript-eslint@v6 and making sure internal builds & downstream repos still compile & lint nicely with all the changes. Let me know if there's anything we can do to help with the v6 upgrade! 💖
The text was updated successfully, but these errors were encountered: