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:closed
  • Created 4 years ago
  • Comments:16 (10 by maintainers)

github_iconTop GitHub Comments

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!

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!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Extending settings.json in VSCode - Stack Overflow
I'd like to check a version of VSCode's settings. json into our team's git repo while still allowing for individual devs to add...
Read more >
Configuring Jest
Configuring Jest. The Jest philosophy is to work great by default, but sometimes you just need more configuration power.
Read more >
Bundling Extensions - Visual Studio Code
The first reason to bundle your Visual Studio Code extension is to make sure it works for everyone using VS Code on any...
Read more >
Config Files - Babel.js
babelrc.json files must be in the root package, by default. This means that, the same way the working directory affects babel.config.json ...
Read more >
Setting Up Your Editor | Create React App
We highly recommend extending the base config, as removing it could introduce hard-to-find issues. · When working with TypeScript, you'll need to ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found