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

Provide support for multi-root scoped workspace variable #10

Open
goerks opened this issue Aug 24, 2023 · 1 comment
Open

Provide support for multi-root scoped workspace variable #10

goerks opened this issue Aug 24, 2023 · 1 comment

Comments

@goerks
Copy link

goerks commented Aug 24, 2023

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:

  "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.

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:

  "vale.valeCLI.config": "${workspaceFolder:doc}/.vale.ini",
  "vale.valeCLI.path": "${workspaceFolder:doc}/build/ext/vale"
hangie added a commit to hangie/vale-vscode that referenced this issue Apr 4, 2024
ChrisChinchilla pushed a commit that referenced this issue Apr 7, 2024
* Fix for issue #33

* Handle multi-root workspace variable - issue #10
@hangie
Copy link

hangie commented Apr 20, 2024

Released in v0.19.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants