Recommend Visual Studio Code extensions along with your code

1

JSONLint

Yes! You can not comment in JSON with // or /**/ or with any character3. JSON doesn't support comments. So, if you try to validate the example with a validator/linter, you will get errors. Do you remember the first image where lines starting with // are in red? This is because parser of Github thinks that there is a syntax error and yes, there is. BUT, VS Code allows comments in its configuration files (like extensions.json) with JSON with Comments (jsonc).4 Therefore, it is valid to have C-like comments in extensions.json. I highly recommend commenting for each extensions like writing purpose of the extension or human readable name of it since some extension names could be little cryptic. If your project CI pipeline runs some JSON linter on all project files ending with .json, this may cause your CI pipeline to fail. Don't forget to exclude extensions.json (if you are adding comments) from JSON linting process if you have any.

#Development #Image Optimisation #Image Editing 131 social mentions

2

Visual Studio Code

Visual Studio Code, VS Code in short, is a very popular editor (my main editor for several years) among many developers 1. Its power is at least doubled by variety of extensions. In this post, I will show you a way of recommending VS Code extensions to developers along with code. The steps are already explained by Microsoft but here I will add my tips.

#Text Editors #IDE #Software Development 1019 social mentions