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
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: