Illuminated Cloud 2

Compatible with: IntelliJ IDEA WebStorm
Feb 15, 2019
62 819

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 (Aura and LWC), 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
  • Refactoring
  • 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 1165 - Metadata denoted as coming from an installed package with no namespace is now available for inclusion in subscriptions and for deployment/retrieval. This should allow users to work with metadata from unlocked packages without namespaces. Note that there will be a second change in the near future that will retain the full bodies of Apex classes denoted as such in the OST so that even if they are not included in project source, they will still be available for perusal and stepping through during offline debugging.
  • LWC deployment error reporting improvements. There are several patterns for these types of errors, and one that includes line/column number information as part of the message itself is now parsed and handled so that the exact reported location is properly linked from the error.
  • Improvements to SFDX scratch org details caching. Details should need to be reloaded much less frequently now and only when actually required.