Influenced by this extension, User Settings.json the whole file loses hover information

[hw770]

Type: Bug

After the latest update of vscode, I found that in my settings.json, hovering on an element just showed nothing except "loading". Meanwhile, other jsonc language feature like auto completion and linter are not working, too.

It's not just the configuration of markdownlint that's affected; it's the configuration of the entire file.

I have never thought this markdown extension could enfluence a json file, but the result of extension bisect convinced me. I tryed to comment all config of markdown lint, but it doesn't work. Only disabling it works.

With clean configuration, markdown lint disabled, no any other extensions installed, the result:

With clean configuration, markdown lint enabled, no other extension, the result:

The keybindings.json is not affectted.

Extension version: 0.54.0 VS Code version: Code 1.86.1 (31c37ee8f63491495ac49e43b8544550fbae4533, 2024-02-07T09:08:20.941Z) OS version: Windows_NT x64 10.0.22621 Modes:

System Info

|Item|Value| |---|---| |CPUs|AMD Ryzen 5 4600H with Radeon Graphics (12 x 2994)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|undefined| |Memory (System)|15.42GB (5.64GB free)| |Process Argv|--crash-reporter-id d7f1dabb-d13d-45d6-b1fd-cac0270b58ac --crash-reporter-id d7f1dabb-d13d-45d6-b1fd-cac0270b58ac| |Screen Reader|no| |VM|50%|

A/B Experiments

``` vsliv368:30146709 vspor879:30202332 vspor708:30202333 vspor363:30204092 vscoreces:30445986 vscod805cf:30301675 binariesv615:30325510 vsaa593:30376534 py29gd2263:30899288 vscaat:30438848 c4g48928:30535728 azure-dev_surveyone:30548225 a9j8j154:30646983 962ge761:30959799 pythongtdpath:30769146 pythonidxpt:30866567 pythonnoceb:30805159 asynctok:30898717 pythontestfixt:30902429 pythonregdiag2:30936856 pyreplss1:30897532 pythonmypyd1:30879173 pythoncet0:30885854 pythontbext0:30879054 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 3ef8e399:30964150 ```

[DavidAnson]

I'm unable to reproduce this behavior. Please close all files then close and reopen VS Code. Open the extension pane and look at the "RUNTIME STATUS" tab for markdownlint - it should say "Not yet activated." which means the extension is not loaded. Now open VS Code's User Settings and switch to text mode - hover over built-in settings and markdownlint settings should work as expected. Try to verify that adding a markdownlint setting offers auto-complete of the setting name and value. Now check the extension's "RUNTIME STATUS" tab again to verify it still says "Not yet activated.". If any part of this does not work, the issue is likely with VS Code since the markdownlint extension was never loaded and its JSON metadata is valid. Please try disabling all other extensions, clearing out all your user settings, and restarting VS Code. If this is still broken for you after that, I'd suggest reinstalling VS Code or trying an Insiders build.

[hw770]

I'm unable to reproduce this behavior. Please close all files then close and reopen VS Code. Open the extension pane and look at the "RUNTIME STATUS" tab for markdownlint - it should say "Not yet activated." which means the extension is not loaded. Now open VS Code's User Settings and switch to text mode - hover over built-in settings and markdownlint settings should work as expected. Try to verify that adding a markdownlint setting offers auto-complete of the setting name and value. Now check the extension's "RUNTIME STATUS" tab again to verify it still says "Not yet activated.". If any part of this does not work, the issue is likely with VS Code since the markdownlint extension was never loaded and its JSON metadata is valid. Please try disabling all other extensions, clearing out all your user settings, and restarting VS Code. If this is still broken for you after that, I'd suggest reinstalling VS Code or trying an Insiders build.

Thanks. Sorry for my misleading. I updated my discription just now. 4 key points:

• It's not just the configuration of markdownlint that's affected; it's the entire settings.json file.
• The keybindings.json is not affectted.
• Disable this extension work well.
• The bug exists even with clean configuration with no extension but markdownlint.

All these seems to suggests that this bug is caused by mdlint. I'm not sure.

Actually, I just disabled markdownlint and left it there these days. I haven't tried to reinstall VS code, but thanks agian.

[DavidAnson]

Please go through the steps I list above and describe the results you get OR provide a link to a GitHub repository that I can use to try to reproduce the problem.