We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using the vale-vscode extension in a multi-root workspace environment. The vale executable to be used is downloaded in the build/ext folder.
build/ext
In the our-repo.code-workspace file, I added this configuration:
our-repo.code-workspace
"vale.valeCLI.config": "${workspaceFolder}/.vale.ini", "vale.valeCLI.path": "${workspaceFolder}/build/ext/vale"
When opening a markdown file in the doc workspace folder it works all fine, as the downloaded vale executable is referenced correctly.
doc
But when I open a file from an other workspace folder, neighter of the files can be found and two errors are thrown.
Could you provide the scoped multi-root workspace variables, so the following configuration is possible:
"vale.valeCLI.config": "${workspaceFolder:doc}/.vale.ini", "vale.valeCLI.path": "${workspaceFolder:doc}/build/ext/vale"
The text was updated successfully, but these errors were encountered:
Handle multi-root workspace variable - issue ChrisChinchilla#10
220ed1a
Fix for issue #33 (#34)
d499576
* Fix for issue #33 * Handle multi-root workspace variable - issue #10
Released in v0.19.0
Sorry, something went wrong.
No branches or pull requests
I'm using the vale-vscode extension in a multi-root workspace environment.
The vale executable to be used is downloaded in the
build/ext
folder.In the
our-repo.code-workspace
file, I added this configuration:When opening a markdown file in the
doc
workspace folder it works all fine, as the downloaded vale executable is referenced correctly.But when I open a file from an other workspace folder, neighter of the files can be found and two errors are thrown.
Suggestion
Could you provide the scoped multi-root workspace variables, so the following configuration is possible:
The text was updated successfully, but these errors were encountered: