Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Uses {# #} instead of <!-- --> for template comments
See original GitHub issueIssue Type: Bug
When you toggle line comments, the extension uses {# #} instead of <!-- --> for commenting code in Vue SFC template tags.
Extension version: 0.34.16 VS Code version: Code 1.67.2 (Universal) (c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5, 2022-05-17T18:20:57.384Z) OS version: Darwin arm64 21.3.0 Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Apple M1 (8 x 24) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled |
| Load (avg) | 6, 5, 4 |
| Memory (System) | 16.00GB (0.07GB free) |
| Process Argv | –crash-reporter-id 6e4ab4f6-2ff7-4100-b5dc-ce1fc869657c |
| Screen Reader | yes |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebug:30492333
vscaat:30438848
vsclangdc:30486549
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Using regular HTML comments instead of Django template ...
Using regular HTML comments (text between <!-- and --> ) in templates causes the Django template engine to render these comments in the...
Read more >Liquid template language - Shopify Open Source
Inline comments inside liquid tags ... You can use the inline comment tag inside liquid tags. The tag must be used for each...
Read more >Using modern comments in Word
The modern comments experience in Word sets the stage for richer collaboration by your team and enables features such as @mention notifications.
Read more >Template:Remark
Usage. Used instead of Template:A note for general comments in an area where decisive comments are made; ie at XFDs.
Read more >Advanced Templates: Comment Tags
A container tag representing a list of the comments posted by visitors to your blog. For each comment, you can use any of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is definitely a misunderstanding. 🤦♂️ Try open a .html file and do comment, you should see
{# #}. (Please don’t live with it:) )Well, I checked all existing issues including the linked and my situation is different. The output in the description is from bisect which correctly identified volar as the culprit.
When I disable volar, commenting works correctly so maybe a regression makes volar change how comments are defined 🤷🏾 ?
It’s only a minor annoyance and I guess I can live with wrong comment formatting given how invaluable volar is for other things.