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

A vscode plugin called vue-official breaks syntax highlighting #4753

Open
QianSeNianHua opened this issue Aug 30, 2024 · 3 comments
Open

A vscode plugin called vue-official breaks syntax highlighting #4753

QianSeNianHua opened this issue Aug 30, 2024 · 3 comments

Comments

@QianSeNianHua
Copy link

QianSeNianHua commented Aug 30, 2024

Vue - Official extension or vue-tsc version

v2.1.2

VSCode version

1.92.2

Vue version

2.7.16

TypeScript version

System Info

System:
    OS: Windows 10
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 4.01 GB / 15.65 GB
  Binaries:
    Node: 14.21.2
    Yarn: 1.22.19
    npm: 6.14.17
  Browsers:
    Edge: 44.19041.1266.0
    Internet Explorer: 11.0.19041.1202

Steps to reproduce

<template>
   <u-popup v-if="a > b" :show="isShow" @close="isShow = false">
      <ResourceList :defaultValue="defaultResource" :data="resourceList" @cancel="isShowResource = false" @confirm="handleConfirmResource" />
    </u-popup>
<template>

<script>
.......
</script>

The above template contains the special symbol “>” and "isShowResource = false", and all subsequent syntax highlighting has no effect.

What is expected?

I disabled the vue-official plugin and it worked.

What is actually happening?

The effect of turning on the plugin
image

The effect after disabling the plugin
image

Link to minimal reproduction

No response

Any additional comments?

No response

@venetc
Copy link

venetc commented Aug 30, 2024

Rolling back to 2.0.28 saves the day.
Happens in 2.1.0 and 2.1.2

@TheDutchCoder
Copy link

I can confirm the latest two versions no longer work. I can't command+click components anymore and they're not highlighted properly.

@davidmatter
Copy link
Collaborator

@TheDutchCoder that sounds unrelated to this issue. Would you please create a new issue with information about your problem and your setup?

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

4 participants