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

Ever since vscode update my component hilighting is broken #4156

Open
maxwellsmart84 opened this issue Mar 25, 2024 · 11 comments
Open

Ever since vscode update my component hilighting is broken #4156

maxwellsmart84 opened this issue Mar 25, 2024 · 11 comments

Comments

@maxwellsmart84
Copy link

image

^^ Using Monokai, all Vue components are now green making it very difficult to read.

@YcZzy
Copy link

YcZzy commented Mar 26, 2024

the same problem as you just install the old version

@maxwellsmart84
Copy link
Author

@YcZzy old version of VSCode or Volar?

@maxwellsmart84
Copy link
Author

Downgrade to 2.6 did fix it for me.

image

@davidmatter
Copy link
Contributor

This is not a bug, it's just semantic highlighting working properly. You can remove it in the settings
image

@Laurelin
Copy link

This is not semantic highlighting working properly; it doesn't recognize components at all. have to revert to 1.8.27 to fix it. Big problem, because it doesn't know what props my components need, makes breaking things inevitable.

@CyberCowboy404
Copy link

I've noticed that my highlight broke after I run code formatting.
After formatting my script section becomes like this

<script
  setup
  lang='ts'
>

This is annoying behavior which I also got after update.
i suppose it may cause such problem

@killjoy1221
Copy link

The highlighting isn't completely broken for me using Dark Modern theme, but it does blink in and out sometimes as I scroll. Specifically, I've seen that if I start to scroll past about 50 lines of <template> code, the highlighting breaks.

@qiaozhu
Copy link

qiaozhu commented Apr 8, 2024

切换折叠、滚动条滚动等情况下,组件高亮会闪烁

@XioDone
Copy link

XioDone commented Apr 12, 2024

@johnsoncodehk
Is it possible to refer to #2252 to fix it?
image

@johnsoncodehk
Copy link
Member

@XioDone No, with TS plugin it can't use "component" semantic token type.

@DocMcCoy
Copy link

DocMcCoy commented Apr 16, 2024

I've been annoyed with this for a minute but while I was messing around I noticed highlighting changing as I changed the lang attribute.

Screenshot 2024-04-16 at 4 08 50 PM Screenshot 2024-04-16 at 4 10 34 PM

js doesn't seem to be the lang that you would want there however. Also interesting is that in both scenarios the built-in TransitionGroup component is highlighted as expected.

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

No branches or pull requests

10 participants