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

Does not detect vale configuration when using multi-root workspace #55

Open
dkwon17 opened this issue Nov 27, 2024 · 0 comments
Open

Does not detect vale configuration when using multi-root workspace #55

dkwon17 opened this issue Nov 27, 2024 · 0 comments

Comments

@dkwon17
Copy link

dkwon17 commented Nov 27, 2024

My project has a .vscode/settings.json file with the following content:

{
    "vale.valeCLI.config": "<absolute path to project>/.custom.ini",
}

When this project is imported in a multi-root workspace in VS Code, my custom value config file .custom.ini is not being used.

To reproduce the problem:

  1. Clone this project: https://github.com/dkwon17/vale-boilerplate/tree/testing
  2. In the .vscode/settings.json file, edit the value of vale.valeCLI.config value so that it is the correct absolute path for your machine
  3. Open VS Code with vale-vscode installed
  4. Open the project as a multi-root workspace by clicking on add a folder instead of Open Folder:
    image
  5. Open the command palette and run Developer: Reload Window
  6. Open the README.md file and notice that there are no vale warnings:
    image

Expected behaviour:
I expected that the behaviour would be the same as when opening the project folder via clicking Open Folder. In this case, the vale configuration is being read and warnings appear:
image

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

1 participant