Vetur: Vetur Vue Intellisense For Vue Template Displaying Red Color But Not Error

Created on 18 Feb 2021 · 5Comments · Source: vuejs/vetur

Issue Type: Bug

After updating VSCode to the January 2021 version, the Vue code that is in the tag partially turns red (because it's usually due to a code writing error). the compile process runs normally without errors. It's just uncomfortable seeing the previously normal code change color (as if it's an error)

Extension version: 0.32.0
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19042

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 x 3592)|
|GPU Status|2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: unavailable_off
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: unavailable_off
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.89GB (11.68GB free)|
|Process Argv|--crash-reporter-id f30efc2b-9351-478a-a544-4975aa18f426|
|Screen Reader|no|
|VM|0%|

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt617cf:30253240
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30256636
pythonvsdeb440:30248342
pythonvsded773:30248341
vstes627:30244334
pythonvspyt600cf:30251589

bug grammar upstream

Source

young-altair

👍4 👀1

Most helpful comment

I have the same issue since the last update.
It seems to be doing if I use the typeof lightbox !== 'undefined' in the template.
When I change it to the (typeof lightbox) !== 'undefined' then the problem disappear.
First way without brackets is valid and vetur should not force us to change the way we are writing the code.