Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

should "extends" work in "settings.json"?

See original GitHub issue

I have global settings for the command line tool in ~/.config/markdownlint/config.

This doesn’t seem to be picked up by the vscode extension by default.

I tried to use "extends" to read it in but it doesn’t seem to work:

"extends": "../.markdownlint.json",

Should I expect this to work or no?

If not, then "extends" should show up as invalid in settings.json.

Issue Analytics

State:
Created 4 years ago
Comments:16 (10 by maintainers)

Top GitHub Comments

1reaction

DavidAnsoncommented, Sep 28, 2020

Please uninstall your custom version and install 0.37.0 - your scenario works fine for me there. Thanks for bringing this up!

0reactions

xeho91commented, Sep 28, 2020

It works for me as well in 0.37.0 with extending ./config/.markdownlint.json. Thank you very much!

However, I am NOT seeing the need to restart VS Code for other changes to ./config/.markdownlint.json to take effect - those are applied immediately. You can look at the Output / markdownlint window to see when config changes are detected and reloaded.

I tested it again (with the new version 0.37.0). The problem doesn’t exist, as long as the name of the file follows the format specified in the docs - as in .markdownlint.json. However, if you change slightly the name, for example: .markdownlintrc.json, then the problem exists. Not a big deal though. We will name the config file as .markdownlint.json. Thank you again!