Illuminated Cloud Announcements

  2.2.9.4 Issue 2468 - Graphical preview of Flow metadata Inspired by  Todd Halfpenny 's wonderful work on a  graphical viewer for Flow metadata  for VS Code, I've implemented similar for IC2. Now by default when you open a  *.flow[-meta.xml]  file in IC2, the default editor will feature a split view with the Flow XML on the left and a flowchart diagram on the right. This is the same IDE split editor component used for Markdown and SVG files and can be toggled to show only the source, only the preview, or both if desired. The preview is  live  and  automatically updates  as the Flow XML file contents change. The JetBrains  Markdown  ( bundled ) and  Mermaid  (freely-available via the  plugin marketplace ) plugins  must be installed  for this feature to be enabled. IC2 automatically assists with installation and enablement of these two plugins if necessary when Flow files are opened. The feature can also...

  2.2.9.3 Issue 2474  - When  Settings | Editor | Code Style | Wrap on typing  is enabled, Apex string literals will no longer automatically wrap as string concatenation expressions in contexts in which a single string literal is required, specifically annotation attribute values,  switch when  literals, and SOQL/SOSL queries. Issue 2475  - Improved logic for matching retrieved metadata files against local files in existing bundle directories. Issue 2476  - Fixed a performance regression introduced in 2.2.9.2 with Tooling API-based single file deployment in projects with Local Files metadata subscriptions. Prospective workaround for  IDEA-340523  where programmatic module facet configuration changes aren't being persisted properly in 2023.3, specifically the automatic migration of Selected and All/Project metadata subscriptions to Local Files metadata subscriptions. This workaround ensures that an unknown subscription type (i.e., one tha...

  2.2.9.2 Issue 2464  - Added support for the missing  lightning-select  LWC component. Issue 2469  - Fixed an issue with a few  Knowledge__DataCategorySelection  field data types that are reported as  DATACATEGORYGROUPREFERENCE  but should be represented in Apex as  String  and in ES6/TypeScript as  string . Issue 2472  - Fixed an issue with incorrectly reported  Active  status indicators for picklist field values in OST custom field ApexDoc. It looks like at some point the API stopped returning a non- null  value for  isActive  for active picklist field values, and IC2 was interpreting  null  as meaning inactive. Major metadata subscription management changes/enhancements  - As promised in the release notes for the previous two builds, this build includes significant changes/enhancements around metadata subscription management. Please read the following carefully to understand how ...

  2.2.9.1 JetBrains 2023.3 (pre-release) support  - At the time of this release, the JetBrains 2023.3 IDEs are still in a  pre-release  state (currently  Beta ). As usual, I have updated IC2 for each pre-release build to ensure compatibility and will continue to do so until the final release, but I'm also unlocking IC2 support for that version even before the final official release. This obviously carries some risk for  early adopters  as there could be breaking plugin SDK changes during the final beta and release candidate phases. If so, I will again update IC2 to accommodate for those breaking changes. While  not recommended , if you choose to move to 2023.3 while it's still in pre-release, you will receive a warning when the IDE is first started about this potentially fragile state. If you encounter issues unique to these 2023.3 pre-release builds, please file a bug in the  public issue tracker  to ensure that I'm aware of them, then ...

  2.2.9.0 Issue 2458  - Fixed an issue that would result in deployment of all of the project's custom labels when deployment is requested for a subset of the project's custom labels. This issue would only occur in source format projects and was the result of a workaround for a bug in the Salesforce CLI's deployment commands when invoked with an explicit list of custom labels that now seems to be resolved. Issue 2462  - Fixed an issue that could occur during OST generation when trying to load a local custom object metadata file with malformed XML. Implemented a few UX enhancements for the dialog used to communicate actions or changes against potentially large sets of files and/or metadata, e.g., conflict detection, adding metadata to a subscription, delete propagation, etc., including: Improved header icon and message layout. The tree view now includes a toolbar with expand all and collapse all buttons. The tree view now supports speed search for type-down searching of its...

  2.2.8.9 Issue 2394  - Added support for a new metadata subscription type,  Local files , that can be used in any IC2 project to infer a metadata subscription from the project's local metadata files, filtering by  .forceignore  if present. This effectively removes the requirement for an explicit metadata subscription—either as a configured selection (metadata format projects only) or a  package.xml  file—for projects configured against non-source-tracked organizations. Note that while any files added to the configured source roots of an IC2 project with this subscription type are automatically considered part of the metadata subscription (again, unless filtered by  .forceignore ), org metadata must still be added to the project using the  Retrieve Metadata  action, typically configured with  Contents  set to  Custom  and  Subscribed Only  disabled. Note that projects configured against source-tracked orgs a...

  2.2.8.8 Issue 2426  - In Apex, it's technically valid to dereference  System.Map.values()  as a single instance of the map's value type, though  only  when the value type is some type of  SObject , e.g.,  accountsByName.values()?.AccountNumber , and  only  when the map has  exactly  one entry. To be blunt, I don't like that allowed idiom for a few reasons. It feels unnecessary and unsafe—pay specific attention to the use of the safe navigation operator before accessing fields of the one-and-only map entry's value—and in order to provide proper support, it muddies the variant code completions offered for the  values()  method to include both instance methods of  System.List  and fields of the map's value type. Having said that, it is allowed and valid, so I've added support for it in IC2's expression type evaluator. Issue 2449  - Added support for email templates created and managed via the Lightning a...