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

Unable to store '.markdownlint.json' in any other location than root #480

Open
NinjaMonkeyGames opened this issue Nov 6, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@NinjaMonkeyGames
Copy link

Description

I want to store my config file in the .config folder not in the root. I am using the following line in my settings.json "markdownlint.configPath": "../.config/.markdownlint.json" I am at a total loss as how to work around this. I believe this to be a bug. If it's not I apologize but would still appreciate some guidance.

Environment

Running client from the store 0.52.0. On the server side 0.13.0 but that's irrelevant to this problem. The --config is fine. It's the VSC extention that's the issue.

MDL Version

0.52.0 (vsc client)

Expected Behavior

When I put the alternative path in the settings.json it should now look for the config in that new location.

Actual Behavior

The client still lints but does not take into account the new config location.

Replication Case

  • Install from the marketplace
  • Create markdownlint.json (Works fine in the root so no need to include my rules here)
  • Add the following line "markdownlint.configPath": "../.config/.markdownlint.json" to settings.json
@NinjaMonkeyGames NinjaMonkeyGames added the bug Something isn't working label Nov 6, 2023
@NinjaMonkeyGames
Copy link
Author

NinjaMonkeyGames commented Nov 6, 2023

I apologise in advance if I have created a duplicate issue. I raised it as a separate ticket yesterday but was unable to find it again. It's possible I did not submit it or something like that.

@DavidAnson
Copy link
Contributor

Link to the issue you opened yesterday: DavidAnson/vscode-markdownlint#307

I replied yesterday as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant