You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 14, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 14, 2023. It is now read-only.
Extension configured but nothing is happening. #117
Hi,
I configured the extension following the instructions here, using the vale-boilerplate repository as an example. I restarted VSCode, but the extension is not active, or at least nothing is showing up in the "Problems" tab and I do not see any squiggly lines. I am not sure how to troubleshoot this.
Using vale from the CLI works well.
Visual Studio Code: 1.76.1
Ubuntu: 20.04
Vale: 2.15.4
vale-vscode: 0.15.3
I'm having the same problem, but I'm not getting the Problems tab. I'm editing a Markdown file and not seeing any feedback! Is there something else I should be doing?
I fixed my problem. Seems it was probably a couple of things. 1.) I had not installed the styles directory, and had not set the extensions in VSCode to their exact locations. 2.) In my .vale.ini file, one of the style folders it was trying to use, the name was incorrect. Found this out when I tried running Vale from the command line, and it reported that error. When I fixed that, it works fine now in VSCode!
Activity
russurquhart1 commentedon Mar 16, 2023
I'm having the same problem, but I'm not getting the Problems tab. I'm editing a Markdown file and not seeing any feedback! Is there something else I should be doing?
russurquhart1 commentedon Mar 17, 2023
I fixed my problem. Seems it was probably a couple of things. 1.) I had not installed the styles directory, and had not set the extensions in VSCode to their exact locations. 2.) In my .vale.ini file, one of the style folders it was trying to use, the name was incorrect. Found this out when I tried running Vale from the command line, and it reported that error. When I fixed that, it works fine now in VSCode!
ivancheban commentedon Mar 30, 2023
This config works for me:
