Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Traverse into type annotations
See original GitHub issueCurrently, we are not traversing into type annotations for either Flow or TypeScript. This is because the nodes on which these properties exist (Identifier, FunctionDeclaration, etc.) are already defined with a set number of children inside of escope, and so it doesn’t search for unknown properties.
Now that we are doing more with type annotations, and the location of type annotation information is more or less standardized for ESTree. I think we should add traversing of these properties. This would basically be:
Identifier.typeAnnotationFunctionDeclaration.returnTypeFunctionExpression.returnTypeArrowFunctionExpression.returnTypeMethodDefinition.returnType
We can modify how escope traverses to include these extra properties.
Breaking: This is a breaking change because changing the traversal depth could have unintended side effects on core or custom rules.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
In the 2016-09-15 TSC meeting, we decided to add traversals for type annotations and decorators in v4.0.
PR up!