The fastest way to run one of your project’s run configurations is to press ⌃⌥R on macOS or Alt +Shift+F10 on Windows/Linux and select one of the configurations from the popup. With the Extend Selection action, you can quickly expand the selected area without using the mouse. However, if you need to replace one suggestion with another, press ⇥ / Tab, and the current element will be replaced with the selected lookup item. The natural thing to do is press ↵ / Enter to select one of the suggestions offered.
#SEARCH ALL FILES FOR TEXT WEBSTORM CODE#
Code completion with replace: ⇥ / TabĪs you start typing in WebStorm, a code completion popup will automatically appear. If WebStorm finds more than one possible declaration of a function, you’ll be prompted to select one from the drop-down list. This shortcut can also help you jump to the referenced file or imported module. With WebStorm, you can instantly jump to the definition of a symbol: just press ⌘ or Ctrl and click on that symbol, or place the caret on it and press ⌘B / Ctrl+B. Go to Declaration: ⌘B or ⌘+Click / Ctrl+B or Ctrl+Click To quickly access the list of available refactorings for the selected code, press ⌃T / Ctrl+Alt+Shift+T. Just like other IDEs by JetBrains, WebStorm is known for its powerful refactoring capabilities. Visit this page to learn more about inspections and what you can do with them. This will disable it for the whole project. Whenever you see a squiggly line in your code or whenever WebStorm displays a light bulb in the editor, you can click on that light bulb or place the caret on your code and press ⌥↵ / Alt+Enter – the IDE will provide you with a list of actions that are available in the current context.Īnd what if you don’t want to use a particular action or see a warning anymore? Place the caret on your code, press ⌥↵ / Alt+Enter, then click the arrow next to the inspection you no longer want to see, and disable it. WebStorm has loads of intention actions to help you quickly apply fixes, generate code, and change the project settings. You can also enable or disable some of the actions right from the popup, as shown in the gif. As the name suggests, it allows you to search everywhere in your project for any files, actions, classes, or symbols, and it will show you all the matches in one place.Ĭlick on the tab you need or press ⇥ / Tab to narrow down the search. If there is just one shortcut you take away from this blog post, it should be Search Everywhere. You can customize your keymap configuration in Preferences / Settings | Keymap.
#SEARCH ALL FILES FOR TEXT WEBSTORM WINDOWS#
Memorizing all of them would be practically impossible, but the good news is that you don’t have to! You can simply start by learning the essential shortcuts below, and you’ll see an immediate boost in your productivity.Īll the key combinations used here are from the default keymaps for macOS and Windows / Linux. WebStorm can save you a lot of time on performing routine actions. Note: This post was updated in June, 2021.
However, it looks like I wasn't clear on what my request was, because VSCode has since implemented a lot of this functionality. I've already submitted a feature request mentioning this in the past, which was closed and suggested as an extension. A command might be useful here as well ( References: Find All References of Folder). When using this on a folder (made available in the context menu), it should show the references for all files inside that folder. Additionally, there should be a command, References: Find All References of File as explained here. This is a very useful feature, and should be made available in the file explorer, for a file's context menu when right clicking it, as explained here. Currently you need to use the "find all references" command on an import path that includes the file. VSCode has this already, but few know about it, and the process for getting to it is unnecessary. This feature refers to three subsets of finding references: VSCode actually already has this partially implemented, but it's hidden and not documented well.Everyone is calling it by different names (users coming from WebStorm will refer to it as "Find Usages").
Everyone is referring to different subsets of the feature.
If you search the issues here on GitHub and on StackOverflow, you'll find that there is a ton of fragmentation around this feature for a few reasons: