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

Vetur Vue Intellisense For Vue Template Displaying Red Color But Not Error #2709

Open
yusrenaltair opened this issue Feb 18, 2021 · 11 comments

Comments

@yusrenaltair
Copy link

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

@newbie78
Copy link

i have same problem:
image
this happen after im update to 1.53 ver

@mrpatricko
Copy link

Yep. +1 here. Same issue.

@OndrejLetacek
Copy link

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.

@yoyo930021
Copy link
Member

yoyo930021 commented Feb 26, 2021

Vetur don't force us to change the way we are writing the code.
This is just a bug that I don't know why........

We need to research it.

@pdesmarais
Copy link

Any update on this? Thanks!

@newbie78
Copy link

newbie78 commented Jun 8, 2021

image
i'm check 70tag of vuetur
but everything stay the same

@s-wolfram
Copy link

Still an issue... with vetur 0.34. I'm patching this by enclosing typeof statement with parentheses: (typeof yocrazy !== 'undefined')

@LeoPenaguin
Copy link

Still an issue in September 2021 with 0.34.1

@lunoware
Copy link

lunoware commented Dec 6, 2021

Still an issue December 6th 2021 with v0.35.0

@akosiyawin
Copy link

Still an issue September 17, 2022 v0.36.0

@xcmx
Copy link

xcmx commented Apr 19, 2023

Still an issue, April 19 2023, with v 0.37.3

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