You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add TextMate scopes for variable.other.object.method and support.variable.method (instead of property) #700
In this example, I'd like to be able to have fref() and completion() be white instead of purple, but that's not an option because they have the exact same scope as .listen(.
As of now, VSCode exposes variable.other.object.property and support.variable.property, so I can make fref white and app purple, since app is a property of a variable and not a local variable. I'd like to be able to do something similar with functions that are specifically members of a variable or class. variable.other.object.method and support.variable.method
Update
I believe variable.function is the scope I was looking for, however it doesn't seem to be supported by VSCode. It is supported in other editors!
Moving upstream to get more feedback. However some parts of this sound like they would require semantic colorization which textmate grammars do not support
The only way to syntactically detect function at its reference location is function invocation so that part is out of scope for this repo. The other part of detecting function as variable.function was something we reverted as part of #443 where we concluded that entity.name.function is more widely used and hence we would use that.
Activity
mjbvz commentedon Dec 28, 2018
Moving upstream to get more feedback. However some parts of this sound like they would require semantic colorization which textmate grammars do not support
sheetalkamat commentedon Mar 20, 2019
The only way to syntactically detect function at its reference location is function invocation so that part is out of scope for this repo. The other part of detecting function as variable.function was something we reverted as part of #443 where we concluded that entity.name.function is more widely used and hence we would use that.