Illuminated Cloud brings the modern feature set of JetBrains' powerful IntelliJ IDEA and
WebStorm IDEs to Salesforce development. Illuminated Cloud not only saves you time with its
intelligent auto-completion for all Salesforce programming languages and metadata types, but it
also recognizes issues in your code and offers suggestions for how to correct them. With
Illuminated Cloud's refactoring capabilities, you'll be able to own and evolve your
Salesforce code base like never before.
Illuminated Cloud provides full support for both traditional and Salesforce DX development
models, allowing you to flow seamlessly between the two models in a single tool. Because Illuminated Cloud
extends JetBrains' powerful IDEs, you can leverage their extensive capabilities including best-in-class Web
application development features (IntelliJ IDEA Ultimate Edition and WebStorm), seamless version control
integration, and first-class integrations with task management and bug tracking systems.
Illuminated Cloud dramatically simplifies development and deployment of Apex, Visualforce,
Lightning, and other Salesforce metadata types with modern IDE features such as:
- Intelligent Code Completion and Time-Saving Live Templates
- Extensive Source Code Navigation and Cross-Referencing
- Code Inspections and Intentions
- Intelligent Source Code Generation
- Content Type-Aware Static Resource Management and Static Resource Bundles
- Integrated API Documentation and ApexDoc Support
- Configurable Source Code Formatters
- Template-Based Source File Creation
- Full Salesforce DX Support
- Offline Apex Debugger
- Integrated Apex Unit Test Execution and Code Coverage Analysis
- Anonymous Apex/SOQL Query Execution and Apex Log Viewer
- Powerful Connection Management
- Offline Symbol Table Generation
- Flexible and Efficient Metadata Management
Recent change notes
Issue 978 - Either partial commits never worked via the Tooling API or there has been a recent regression in that functionality. Either way, IC now treats successes reported by otherwise failed container async requests as not having occurred from a state tracking/reporting standpoint. I have raised this issue with Salesforce to determine whether this is original/intentional behavior or a regression. If/when the Tooling API properly supports partial commits, this can be reverted.
Issue 1015 - Namespace substitution and deployment/retrieval substitution rules are now applied to static resource bundle contents are they are archived as static resource files for deployment and extracted back into bundles as a result of retrieval respectively.
Issue 1020 - Fix for issue where the timestamps used for conflict and dirty tracking might not be computed properly when the org and local workstation are not in the same timezone. This problem was found while working on working on issue 1020 and may or may not be a fix for that bug, but it's certainly something that needed to be addressed.
Issue 1024 - Fixed an issue where expired/deleted scratch org information could be cached in memory until the project was closed/reopened or the IDE restarted. Now when a scratch org with a particular alias is replaced, IC should pick up the change immediately.
Issue 1040 - Changed lightning:textArea.maxLength to maxlength. As always, the IDE caches the XSDs used for Visualforce/Lightning elements and their attributes aggressively, so you'll likely need to use Ctrl+B/Cmd+B on any existing reference to an element in the lightning namespace to force the cache to rebuild.