Skip to content
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

February 2020 update broke typescript and javascript syntax #132

Closed
sergejostir opened this issue Mar 10, 2020 · 23 comments
Closed

February 2020 update broke typescript and javascript syntax #132

sergejostir opened this issue Mar 10, 2020 · 23 comments

Comments

@sergejostir
Copy link

There were some changes introducted in February 2020 that break highligting for JS.

More info: microsoft/vscode#92308

@leandrocunha
Copy link
Contributor

You are right @sergiz a strange behavior for me here. Look the component written in white color:
Screenshot 2020-03-10 at 09 46 51

@DoanVanThuong
Copy link

DoanVanThuong commented Mar 10, 2020

image
Same issue

@sergejostir
Copy link
Author

sergejostir commented Mar 10, 2020

Of course you have the same issue, it affects every single theme out there which is not adjusted to the new method.

I opened this issue to bring it to attention of the maintainer. For now you can simply use the "fix" from the link above.

@dsifford
Copy link
Member

I'll look into this later this afternoon and push out a fix.

In the meantime, can someone comment a section of code that I can copy paste to reproduce? (screenshots are helpful, but written code is easier!)

Thanks!

@dsifford dsifford changed the title February 2020 update adjustment needed February 2020 update broke typescript and javascript syntax Mar 10, 2020
@dsifford dsifford added the bug label Mar 10, 2020
@dsifford
Copy link
Member

Update: still waiting for my distro's package repository to push out the update for vscode. Can't repro til that happens. Should be in the next day or two.

@sergejostir
Copy link
Author

I'll look into this later this afternoon and push out a fix.

In the meantime, can someone comment a section of code that I can copy paste to reproduce? (screenshots are helpful, but written code is easier!)

Thanks!

Basically any JS code.

console.log()

already has wrong highlighting.

@dsifford
Copy link
Member

Got it, thanks!

@DoanVanThuong
Copy link

editor.semanticHighlighting.enabled": false

it work for me

@EduardoAraujoB
Copy link

Captura de tela de 2020-03-11 14-02-14
the test colors broke with this new vscode update

@dsifford
Copy link
Member

Still waiting for my distro to push the vscode update, but when that happens I'll have a fix pushed out shortly after.

@EduardoAraujoB
Copy link

Ok, thanks

@EduardoAraujoB
Copy link

editor.semanticHighlighting.enabled": false

it work for me

worked for me too

@dsifford
Copy link
Member

Just don't forget to re-enable that when the fix gets pushed out. That's gonna be a killer feature!

@EduardoAraujoB
Copy link

Nice, I will re-enable it later

@JimmyMultani
Copy link

Hey @dsifford, has your distro pushed an update yet?

@dsifford
Copy link
Member

Ugh, no! Getting pretty annoyed and might have to download insiders or something in the meantime.

@dsifford
Copy link
Member

@JimmyMultani Update: just compiled it myself and i got the update finally... I'll look into these issues later this evening or tomorrow at the latest.

@dsifford
Copy link
Member

Okay, so here's the bummer... It doesn't appear that this is actually fixable beyond turning off semantic highlighting right now.

I quickly combed through some of the issues checking syntax groups and they are all being highlighted correctly, when identified correctly. The issue is, however, that there is some inconsistencies with identification (using react as an example: class components vs function components are highlighted differently).

So, for now, I'll keep this open, but there's not much more I can do until the issue is sorted out upstream.

@JimmyMultani
Copy link

JimmyMultani commented Mar 18, 2020 via email

@dsifford dsifford removed the bug label Mar 18, 2020
@JimmyMultani
Copy link

JimmyMultani commented Mar 18, 2020

FYI @dsifford, the latest VSCode update now defaults semantic highlighting to false. So the issue is no longer present.

microsoft/vscode#92740

@sergejostir
Copy link
Author

So this can then be turned into a feature request to make Dracula theme support semantic highlighting.

@dsifford
Copy link
Member

@sergiz It's on my radar. Plan on deep diving this when i get some extra time (possibly this weekend).

@sergejostir
Copy link
Author

I guess that this has already been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants