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.
Format of generated config file conflicts with what `deno fmt` prefers
See original GitHub issueOn initializing, the plugin generates a config JSON file with 4-space indent, but it conflicts with deno fmt since it prefers 2-space indent. It is a kind of annoying that running deno fmt formats .vscode/settings.json just after it’s generated.
It would be better if we could make the plugin generate a JSON file whose format deno fmt likes.
However, from my quick browse, unfortunately it seems like the VSCode Extension API doesn’t provide a way of configuring the indent size of config files. https://code.visualstudio.com/api/references/vscode-api#WorkspaceConfiguration
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I suspect some people would want to
deno fmtthe file, right?Moved the issue to deno then. 🤷