-
Notifications
You must be signed in to change notification settings - Fork 352
Quoted string as object key not supported #477
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
Comments
This is probably the result of your color scheme. We've added a lot more syntax granularity, but it's possible your color scheme isn't matching up to these links well. Can you link me to your color scheme file and I can look into perhaps better link things up? |
Hmm, interesting. I'm using gruvbox. |
Huh, it looks like it might just be that one file, not a universal problem. Here's a different file, same Vim config Things look pretty normal there, so maybe it's just a problem with the first file I showed. Could it be that the red mark on that line that starts with |
Ahah, I think I can see the issue in your first file. It's a type of ES6/7 syntax I never thought to support. var obj = {
'key-name'() {}
}; For now, if you changed it to: var obj = {
['some-key']() {}
} Then it should fix itself. I will work on supporting that string key into parentheses syntax shortly though. |
Alright, cool. It's not something I can change in my codebase, but I'm glad to know it'll be handled sometime soon. |
I have a fix for this that is going into |
Awesome! Thanks for the quick turn-around there, I'll install from Edit: Just installed it, that fixed my problems! |
Awesome, closing this, as this fix will be going out shortly. |
Thanks again for the quick turn-around! |
This is fixed in |
Since pulling the updates from today, my highlighting has been way off.
None of the
const
s are highlighted anymore, as are... Well, most other things. It was all fine beforedevelop
was merged in today.Edit: It's been determined that the issue is specifically with the following kind of syntax
The text was updated successfully, but these errors were encountered: