![]() ![]() With one quick view, you can determine that there are four parameters and each name is much more readable than before.Īs I said before, this formatting works also in JavaScript, TypeScript, CSS, HTML, JSON and many more languages. foo(Īll parameters are separated into an individual line of code, giving you the best readability to track the possible options. With Perrier installed and configured, you hit Format and the previous code is automatically formatted to something like the following code section. Every software developer has a slightly different, or occasionally a very different, style. Such functions tend to be hard to read and more error-prone because you can quickly lose track. foo(reallyLongArg(), omgSoManyParameters(), IShouldRefactorThis(), isThereSeriouslyAnotherOne()) It might look like the following code section. Imagine a function with a couple of parameters which does have a long name as well. A comprehensive list is available on the official documentation. ![]() Well, I have to admit the default configuration is already excellent, so I usually haven’t much to amend. Once you figured a decent configuration out, you can lean back and never care about formatting anything again. It does all the magic of automatic code formatting with a breeze. Prettier is probably my most favorite extensions of all time. This feature is super neat when you browse over different code sections. You see who and when the last change was made. Like the Current Line Blame shows the last editor of a source code line, the Git Code Lens features always displays the author on a code block. Git Code LensĪll the relevant information is right there. You tumbled over a line of horror from the past, and you want to blame someone right away? Just move the cursor in the line to see, that you committed that crime a couple of years ago. Don’t waste any more time navigation through Git when you can simply do it with GitLens. It was never easier to comprehend the history of the source code. When did this bug first come into the code base? With revision navigation, you can browse through the complete Git history of the current file. ![]() GitLens is Open-Source and the source code can be found on GitHub. Even if you don’t use Visual Studio Code, you can install GitLens for several IDEs. This extension, like the name suggest, brings countless functionalities and visual representation to Visual Studio Code. I am sure I don’t have to explain the benefits of a VCS, but if you use Git with Visual Studio Code, you have to install the GitLens extensions. Let’s be honest, if you really care about your source code, you are probably using some kind of Version Control Software (VCS). Anyway, I believe one or the other item of my list will make it into yours, so let’s start with the first pick. Nowadays, you don’t need any extension for displaying the bracket pair, simply turn it on in the Visual Studio Code settings with "": true. Over the years, many features from third-party developers have become a backed-in functionality – like the famous Bracket Pair Colorizer. Just right after the beginning of the new year, I have gathered my top five most useful Visual Studio Code extensions for 2022. Everyone loves a good Visual Studio Code extensions, and so do I. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |