-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
Type annotations are incorrectly labelled as variables in TM scopes #66149
Comments
Foxhoundn
changed the title
Sometimes, type annotations are incorrectly labelled as variables in TM scopes
Type annotations are incorrectly labelled as variables in TM scopes
Jan 7, 2019
Please share the text of the code along with all screenshots |
For obvious reasons I can't share all of the code, all you need to do is create a file with const someFunction = something(
async (
asg: string,
sagsag: string,
asgasgsag: string,
aaa: string,
wwqewqewqe: string
) => {
// ...
}
) And it happens |
mjbvz
added
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
grammar
Syntax highlighting grammar
labels
Jan 9, 2019
Thanks. Opened microsoft/TypeScript-TmLanguage#705 to track this upstream |
Any word on this? This is really annoying in Python :( I assume it is the same issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to Reproduce:
variable.other.readwrite
It works fine if at least one of the parameters is inline
Also! The
async
modifier is labelled as function call, which is incorrect as well.Does this issue occur when all extensions are disabled?: Yes/No
Yes
The text was updated successfully, but these errors were encountered: