Quick definition (Ctrl + Shift + I / Opt + Space or Cmd + Y) - View the definition of the current identifier without having to navigate to it.
The current parameter is even highlighted as you move through the invocation arguments. Parameter info (Ctrl + P / Cmd + P) - View the allowed parameters of the current method or function. Quick documentation (Ctrl + Q / Ctrl + J) - Integrated API documentation is a huge timesaver, even more so when you spend the time to document your own APIs via ApexDoc, JSDoc, and documentation metadata. It's by far the fastest way to select exactly what you want. In particular place the cursor on the first line of a statement or class/method declaration and increase the selection. Increase, decrease selection (Ctrl + W / Opt + Up, Ctrl + Shift + W and Opt + Down) - Just try this one and you'll see what I mean. Navigate back/forward ( Ctrl + Alt + Left/Right, Cmd + Opt + Left/Right) - Use browser-style navigation to move back and forth through navigation drill-down paths. Show usages (Ctrl + Alt + F7 / Cmd + Opt + F7) - Quickly see and navigate to usages of the current identifier without opening new docked windows. Go to related (Ctrl + Alt + Home / Ctrl + Cmd + Up) - Quickly navigate between related files, e.g., source and meta.xml files, Lightning bundle files, Visualforce pages/components and their controller classes, Apex product classes and the unit test classes that verify them, etc. Go to declaration, implementation (Ctrl + B / Cmd + B, Ctrl + Alt + B / Cmd + Opt + B) - Quickly navigate to the declaration or concrete implementation(s) of the current identifier. Go to type, file, or symbol (Ctrl + N / Cmd + O, Ctrl + Shift + N / Cmd + Shift + O, Ctrl + Alt + Shift + N / Cmd + Opt + O) - Quickly navigate to an Apex type/trigger, metadata file, or identifier (method, field, etc.) by name. However, ignoring the keys that are common to virtually all application (save, cut/copy/paste, select all, next/previous word, etc.), I would recommend that users incorporate the following into their standard development workflows: That's an incredibly difficult question to answer as I honestly use almost every one of the keys listed above on a daily basis. I'm often asked which handful of keys are the most important to learn in terms of increasing productivity. To ease the transition for those coming from other IDEs and editors, IDEA includes alternative keymaps that mimic the behavior of tools such as Eclipse, NetBeans, Visual Studio, and Emacs.
The following table lists the actions that are explicitly supported by Illuminated Cloud and the default keymap assignments in Windows, Mac OS X, and Linux:įull descriptions of the default keymaps are available from JetBrains.
Using a development tool like IntelliJ IDEA/PhpStorm/P圜harm/RubyMine/WebStorm without learning and/or using the shortcut keys is missing half of the point! I highly recommend that you take the time to learn the keys, and you'll be amazed at how efficiently you write new code and how quickly and thoroughly you gain an understanding of your code base.
I'll let my own bias show through a bit here. These actions can be performed using keyboard accelerators, menu items, and toolbar buttons. This means that the exact same mechanisms for performing an action in Java, Javascript, HTML, CSS, etc., are used to perform the same action in Apex, Visualforce, Lightning and other Salesforce metadata. As a result, most of Illuminated Cloud's features simply apply the base IDE's powerful feature set to Salesforce source file types. Illuminated Cloud extends the base JetBrains IDE's existing functionality to support Salesforce development. How do I use feature X/Y/Z in Illuminated Cloud?