👋 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.
If you really want to "progressively enhance" lint rules, parserServices.program will be null 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! 💖
Thank you for sharing it. That code still remains, but we added tests in #548 and it seems to be working without any problems.
So I'll close this issue.
👋 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 https://github.com/typescript-eslint/typescript-eslint/issues/7124: I see this repo contains references to
hasFullTypeInformation
. That property is something we've never recommended using (see that issue & https://github.com/typescript-eslint/typescript-eslint/issues/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! 💖