2.3.3.3 release notes

2.3.3.3

  • Issue 2632 - Winter '25 / API v62.0 updates
    • Updated the API version used for primary communication with Salesforce APIs to 62.0.
    • Added 62.0 as an available API version number for configured connections.
    • Updated the OST version number to prompt regeneration for system API changes in API v62.0.
    • Updated the bundled completions?type=apex Tooling REST API response to be based on the API v62.0 REST endpoint.
    • Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Winter '25 changes.
    • Updated the bundled SLDS CSS and SVG icons to 2.25.1.
    • Updated for new org features, standard value set names, metadata XML file type extensions, etc.
    • Updated all integrated API documentation.
    • Fully integrated the new Local Development Server feature. I've recorded a demonstration video showing the features of this integration including the following:
      • Added a new run configuration type for integrated execution of the local development server from within Illuminated Cloud. This new run configuration type includes the following options:
        • The connection against which the local development server should run. Note that only CLI-based connections are supported.
        • The optional Lightning Experience application for which the local development server should run.
        • The optional Experience Cloud site for which the local development server should run.
        • Note that if no application or site is selected, the server is executed for the entire org. Application and site selection are mutually-exclusive; only one can be selected for a given run configuration.
      • Added context menu actions and code intentions for quickly creating and launching local development server run configurations for all device types — Desktop, Android, and iOS — supported by the host operating system. Desktop and Android are supported on all OSes (well, for completeness' sake, Android emulation is not yet supported on Windows/ARM64...which just so happens to be my daily-driver these days).; iOS emulation is only supported on Mac. Note that mobile options aren't available when previewing Experience Cloud sites. When starting a local development server for a mobile device type, the user is prompted for a configured device ID for which the respective emulator should be executed. These actions take into account the selected file(s) to create/run the appropriate run configuration by automatically setting the Lightning Experience application or Experience Cloud site option if applicable.
      • Added code intentions for quickly stopping and restarting the running local development server.
      • Added a new Validation and Deployment sub-option of Deploy on save, Disable deploy-on-save of LWC source files when local dev server is running, that, when enabled, does not deploy LWC HTML, JavaScript, and CSS files when the local development server is running and the user types the Save All IDE keyboard shortcut. Note that other deployment methods such as Force Save, Deploy All/Modified Metadata, and Push Metadata can still be used to deploy these files to the server when this option is enabled. Defaults to enabled.
      • Note that xcrun must be in the system execution path for iOS emulation, and advmanager must be in the system execution path for Android emulation.
    • Updated the Apex Control Flow Analysis code inspection to flag attempts to modify Apex List and Set collections during iteration as errors.
    • Added grammar support for negative SOQL currency literals.
    • NOTE: There are a few things that are not currently in this seasonal platform release update build:
      • Salesforce has not yet made Winter '25 / API v62.0 SOAP WSDLs available, so IC's SOAP API clients are still based on API v61.0. Once those are available, I will include them in the immediate next IC update.
      • This update does not yet include support for LWC component development using TypeScript. I have most of this implemented but hit enough snags along the way due to the very early state of this feature that it wasn't feasible to include a reasonable implementation in this build. I've made enough progress, though, that I'm hoping to be able to include a first version of the feature in the next build, or at least one in the very near-term.