

You can also see declaration at the tooltip while keeping Ctrl+Shift pressed: Keeping Ctrl+Shift pressed, point to the symbol, and click when it turns into a hyperlink. You can also see declaration at the tooltip while keeping Ctrl pressed: To navigate to the type declaration of a symbol: place the caret at the desired symbol and choose Navigate | Type Declaration or press Ctrl+Shift+B / Cmd+Shift+B. Keeping Ctrl pressed, point to the symbol, and click, when it turns to a hyperlink. To navigate to the declaration of a symbol: place the caret at the desired symbol and choose Navigate | Declaration or press Ctrl+B / Cmd+B or click the middle mouse button.
#PHPSTORM GO TO LINE CODE#
Navigate to the location where a particular named code reference (a symbol) has been first declared. Go to declaration or type declaration of a symbol.Press Ctrl+Shift+Alt+N / Cmd+Shift+Alt+N to invoke this: Quickly navigate to the desired symbol specified by name. Quickly navigate to the desired class specified by name. Press Ctrl+Shift+N / Cmd+Shift+N to invoke this: This navigation honors CamelCase and snake_case capitalization, as well as wildcards.

The IDE suggests a list of matching names from which you can select the one you need and open it in the editor. Quickly navigate to the desired file, specified by name. Press it one more time to include the non-menu commands in the suggestion list: Choose Help | Find Action from the main menu or press Ctrl+Shift+A / Cmd+Shift+A. Find the desired action without digging through menus or toolbars (covers the commands of the main menu and various context menus, commands performed through the toolbar buttons of the main toolbar and tool windows). This functionality is available in IntelliJ Idea, P圜harm, WebStorm, PhpStorm, RubyMine, AppCode. Here we provide an overview of must-know navigation methods that JetBrains IDEs offer. This time should be minimized as much as possible.įor this reason, a smart IDE aims to guide you around your code, to help you keep up your coding pace, and not scroll thousands of source code lines just to find something you need. If there’s a key metric for being productive and efficient while coding, it has to do with cutting the time you lose on side actions such as configurations, line/file/class search, navigation, etc. It’s easy to lose direction when you move and always have to think where to find the one line or place in code you need right now. You constantly move around your project – switching between editor tabs, navigating to files, directories, classes, functions, comments, declarations, and so on and so forth.
