The problem is that Double SHIFT is not a possible command in VS Code, so since the plugin overrides the VS Code keymap, you end up without being able to open a file neither with Double SHIFT nor CMD+P. You cannot open files with a shortcut! In the JetBrains suite you hit Double SHIFT to open a file, the equivalent in VS Code would be CMD+P. I must say that there is an IntelliJ IDEA keybinding plugin, but it has a huge bug in my opinion. It's not the same, it's not as fast, but it's all we have when working with with VS Code. With these two combined with CMD+F to search in the file and CMD+SHIFT+F to search everywhere it does the trick more or less. Why these shortcuts? Well, I used to work with Jira a lot and these were the commands to move through tickets in a search 🤷♀️. So in this case it would be 'Add Selection To Next Find Match' shortcut from CMD+D to CTRL+J and 'Add Selection To Previous Find Match' to CTRL+K. Actually we had to override one of them when setting the new Delete line command. Navigation: Although we cannot navigate by clicking on methods/classes, there are a couple of shorcuts to go to the previous/next find match. By default CMD+7 is the shortcut to go to your bookmark number 7 in JetBrains (you could bookmark lines), but I didn't use it so I find it more useful this way. To be fair this one is exactly the same, but I had it modified in WebStorm as well. Toggle line comment: From CMD+/ to CMD+7. To make it more readable I'm going to use just CMD instead of CTRL/CMD since I work with a Macbook.ĭuplicate line: In VS Code the setting is usually copy line up/down with SHIFT+OPTION+UP/DOWN but I prefer to use CMD+D to duplicate the current line/selection just like in WebStorm.ĭelete line: From SHIFT+CMD+K to CMD+Del. So what I did to make the migration process less painful was to keep the shortcuts that I use the most. There are some keyboard shortcuts that once you get used to them, you just can't change them. One of the things that made me go back to WebStorm in the past was the shortuts. I also have Vetur for Syntax-highlighting among other features to help coding with Vue. In my case, I work with Vue so I'm using Vue VS Code Snippets. There are several snippets for VS Code depending on the framework you work with. With WebStorm you could create components with the UI, so you could add a new Vue component, or Angular component, with the base structure empty in the created file. This plugin does the trick by adding a toggle button to your interface. For once I got used to a button instead of a shortcut. You can open the terminal on VS Code with a shortcut, but in WebStorm there's always a tab for that. This plugin is even better cause you can list the TODOs, the BUGs, etc. With JetBrains there is always a TODO tab that lists all the TODOs in the project.
Webstorm vs intellij windows#
With WebStorm or any JetBrains IDE you just right click on any file and go to Local History > Show History and a new windows pop ups with all the changes you've made, so if you want to back an hour ago, you can! Just a minor reminder with this plugin, add. I can't count how many times this has saved the day. VS Code comes with no UI for git, but these two plugins are really helpful to fill some of the features. I'm not going to explain how they work, since they have a really good description in their respective marketplace pages.
This is my setup to boost your productivity working with VS Code if you're used to working with WebStorm. The truth is that I wasn't using the right setup for me.Īt Codegram most of the team use VS Code, on twitter there are many people that I follow (and that I look up to) that use it too, so the real question is, why not? I had given several tries in the past, why not another one? The migration setup
But every time I tried to use VS Code in my job, I ended up frustrated, but it was because I wasn't feeling productive. I just used VS Code for personal projects mostly to try something new, both the IDE and the project itself. Since then, I've been working mostly with IntelliJ for the backend stuff and WebStorm for the frontend. When I began to work as a developer, my IDE was Eclipse until one awesome day I discovered the JetBrains suite and it was love at first sight. You can do the exact same thing with many different tools, but with your favourite one you just do it faster and better, it boosts your productivity. And this is perfectly normal, you feel more productive and everything feels really easy to do. Jokes aside, it's a fact that when we get used to working with a specific tool, in the end we all tend to fall in love with it. But after all this time and all the experience behind us, I think we're both more mature now and it's the perfect time for this relationship to finally work. We've broken up and got back together so many times I can't even tell. My story with Visual Studio Code (aka VS Code and vscode) hasn't been the typical love story but more of a toxic relationship.
0 kommentar(er)
