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
// An exceptionally useful commentfunctionfunc(param){vartext='string';for(vari=0;i<param.length;i++){text+=i;}return{"text": text,"boolean": false};}
The entire function contents is scoped with .token.function.meta.js, meaning if a style exists for this, which it does for several themes, this is what they do:
Microsoft Predawn theme
I believe this is the reason some people have pointed out about broken JavaScript text highlighting. Switching to the Atom JavaScript grammar removed the issue as the entire function block is not scoped as such.
Any movement on this? This is also related to an issue I'm seeing in TS where the parameters are not being scoped correctly when using a converted sublime theme as they have the function scope.
For this function:
The entire function contents is scoped with
.token.function.meta.js
, meaning if a style exists for this, which it does for several themes, this is what they do:Microsoft Predawn theme
![image](https://cloud.githubusercontent.com/assets/2193314/16856542/7daf7336-49cf-11e6-83ec-fcfb5ab4578e.png)
I believe this is the reason some people have pointed out about broken JavaScript text highlighting. Switching to the Atom JavaScript grammar removed the issue as the entire function block is not scoped as such.
/cc @aeschli
The text was updated successfully, but these errors were encountered: