Illuminated Cloud Announcements

  2.2.2.2 Issue 630  - Added support for Apex code style configuration for comments. Under the  Comments  tab of  Settings / Preferences > Editor > Code Style > Apex , you can now configure the placement and whitespace handling of line and block comments added using the  Comment with Line / Block Comment  actions. Issue 1271  - Evidently there's a small window of opportunity after unit test execution during which  ApexTestResult.ApexLogId  can contain a log ID that doesn't yet correspond to a row in  ApexLog . I added a limited number of short interval retries when querying unit test logs to narrow (ideally close) this window of opportunity such that logs are properly resolved for executed unit tests when this occurs. Issue 2089  - Fixed an issue that would occur when using the IDE's move refactoring to overwrite an existing project source file. Issue 2093  - Fixed an issue with removal of server-only metadata using the  Delete Metadata  action. Issue 2105  - Prosp

  2.2.2.1 Even more JavaScript and TypeScript editor experience improvements  - Implemented another round of strongly-typed development improvements for JavaScript and TypeScript, this time in support of not just LWC but also Aura and Salesforce Functions. Once again, these improvements are only applicable when IC2 is paired with a commercial JetBrains IDE. Issue 2111  - Enhanced the  Add type hint  code intention to support property getter functions in addition to fields and local variables. Added strong typing for  this[NavigationMixin.GenerateUrl](...)  which should be of type  Promise<URL> . Added a framework indexing handler for  Aura  JavaScript source files that automatically infers the data types of component, event, and helper parameters of functions in Aura controllers, renderers, and helpers. Parameter types in controllers and renderers are inferred based on the parameter index. Parameter types in helpers are inferred based on naming, specifically  component  and  cmp

  2.2.2.0 More JavaScript and TypeScript editor experience improvements  - Implemented another round of strongly-typed development improvements for JavaScript and TypeScript, again primarily focused on LWC development use cases. Again, these improvements are only applicable when IC2 is paired with a commercial JetBrains IDE. Issue 2102  - Added support for code completion and references for  $ fieldOrPropertyName  expressions in wire decorator configuration string literals. Note, however, that completions and references are not currently supported for expression variants (i.e., chained expressions after dots), only for the first expression. Functions which return HTML elements, e.g.,  querySelector*  and  createElement , now return the most specific type of element that can be determined from the provided argument. For standard LWC components this is the component-specific subclass of  LightningElement . For custom LWC components this is the default exported  LightningElement  subclass

  2.2.1.9 JavaScript and TypeScript editor experience improvements  - Implemented a number of significant enhancements for JavaScript and TypeScript development, primarily in support of Lightning Web Components, though some can also be leveraged in Visualforce, Aura, and Salesforce Functions. For more details see  this demo video . NOTE:  Because most of these enhancements are implemented as extensions to JetBrains' native JavaScript and TypeScript language support features, they are only available when Illuminated Cloud 2 is paired with a commercial JetBrains IDE and do not change the behavior of JetBrains' free Community Edition IDEs. Issue 696  - The generated OST now includes TypeScript type definitions for all org SObjects for use in JavaScript and TypeScript. These type definitions are generated into the  TypeScript  sub-directory of the OST which is not considered a namespace in other Salesforce development contexts, and they do not need to be explicitly imported to be u