Illuminated Cloud 2

Compatible with: IntelliJ IDEA WebStorm
Dec 05, 2018
45 332

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
  • 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

Download plugin

Recent change notes

Issues 1170/1171 - The previous build's update for the Winter '19/API 44.0 behavioral change around Flow metadata didn't properly take into account projects staying on API versions prior to that. Things should now work properly for pre-44.0 API versions as well as 44.0+ API versions.