-
-
Notifications
You must be signed in to change notification settings - Fork 596
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
Vue components don't get highlighted like React #1963
Comments
Will this feature be added? so should I close this issue |
Would be great to have it! |
@max-programming don't close it, otherwise they will forget about it. We have to be patient and let them do their work. |
okay. Thanks to support! I think they are working on it. |
@octref I can't see it on mine. Do I have to change some settings? |
@max-programming works for me, It only works for |
It only works for |
@octref Very happy to see the dedication and work towards this extension. Thanks a lot 😊 |
@max-programming Thanks for catching the cases 👍 #2146 |
This issue is finally solved. Sorry I checked it now |
What is the correct scope to change the color in a custom theme? Thank you |
|
How disable this feature?) |
|
Is there some setting that I should check? Or some specific theme? For me, it isn't working. I'm using Vue 3 with Typescript, Community Material Theme and that's it. No highlights. But React highlights works. |
Found the issue (for me). I use WSL 2. When I open a project through WSL it doesn't get highlighted but when I open it through Windows it works perfectly. Edit: |
@mathewcst You might want to file an issue for them: https://github.com/Microsoft/vscode-remote-release |
Info
Problem
I love using Vetur. It is very fast and great. But when I do a React project, and in the highlighting, I saw that the components had a different colour (That is by VS Code) than the normal tags:
I noticed that Vue files did not have that thing:
Reproducible Case
It would be nice if the Vue components also have different colour highlighting
The text was updated successfully, but these errors were encountered: