Illuminated Cloud Announcements

  2.3.0.1 Major restructuring of the IC code base  - This build includes the results of a long-desired restructuring of the IC code base to orient things along discrete feature boundaries. Without going into too much detail, the Salesforce platform has evolved tremendously over the past decade since IC was first started, e.g., Visualforce → Aura (then just called "Lightning") → LWC (also loosely termed "Lightning"); the introduction, release, and ongoing evolution of Salesforce DX; the introduction, release, and recent sunsetting of Salesforce Functions; etc. Features that related to one another in a more simple fashion early on, e.g., Visualforce/Aura and, later, Aura/LWC, no longer had such simple relationships after years of evolution and refinement. In many places, though, the IC code base still reflected those earlier, simpler days, often resulting in indistinct boundaries between distinct features. Starting with this build, feature boundaries are  very  well-d...

  2.3.0.0 Issue 2494 - Spring '24 / API v60.0 updates (follow-up) Salesforce provided the API v60.0 WSDLs which have been used to update the SOAP API client and  metadata.xsd  used for XML metadata file validation and code completion. Other minor fixes and improvements.

  2.2.9.9 Issue 2494 - Spring '24 / APIv60.0 updates Updated the API version used for primary communication with Salesforce APIs to 60.0. Note that at present, I have not yet received the API v60.0 SOAP WSDLs from Salesforce. Once those are available, I will update IC2's SOAP client to be based on those WSDLs. However, I have not seen any issues with using the API v59.0-based SOAP client against the API v60.0 SOAP endpoints. Added 60.0 as an available API version number for configured connections. Updated the OST version number to prompt regeneration for system API changes in API v60.0. Note that Salesforce has implemented some caching-based optimizations to the  completions?type=apex  Tooling REST API in API v60.0 that should result in faster OST generation times than in the recent past. Based on my own measurements, I'm seeing that the response time for that particular API call has dropped from ~1.5-2 minutes to ~30 seconds. Be aware, though, that the very first call to...

  2.2.9.8 Issue 289  - Added a  Save Logs  toolbar button to the Log Analyzer tool window. When one or more logs are selected in the log header table, you can now click this toolbar button to save them as local files in a designated directory. The resulting files are named  ApexLog_LOGID.log .  NOTE:  Once log files are saved locally, IC2 is  no longer responsible for them . If they contain  sensitive or proprietary information , it is the  user's responsibility  to remove or otherwise manage them to avoid potential exposure of that information. Issue 2491  - Updated the Apex parser to handle SOQL currency literal values properly. Issue 2492  - Added a new configuration option,  Illuminated Cloud | Configure Application | Salesforce DX | Ignore warnings on push , that when enabled ( disabled by default ) executes the  force:source:push  command with the  -g/--ignorewarnings  flag. Note that this op...

  2.2.9.7 Issue 2400  - Implemented a workaround for those experiencing OST generation failures due to: Status code 500 returned trying to retrieve .../completions/?type=apex This type of failure has become more prevalent and consistent in the past few days due to an issue that Salesforce has confirmed to be a bug in certain orgs, specifically those that include the  industriesintegrationfwk  namespace. The workaround included here uses a bundled copy of that API response from a "kitchen sink" org, i.e., one where as many optional features are enabled as possible. The resulting OST includes all core standard Apex types and should generally work fine for Apex development, but it will not accurately reflect the target org's set of enabled features and their corresponding Apex APIs, though it should be a superset and not a subset. Once Salesforce provides a fix for this bug, it should just be a matter of generating a new OST to include only the standard Apex types appro...

  2.2.9.6 Issue 2484  -  .forceignore  filtering is now applied when collecting bundle files for deployment directly via the Metadata API. Note that there may still be a gap with regard to this issue if it's in the context of a metadata format project where  .forceignore  filtering is  not  currently applied at all. Issue 2486  - Addressed several missing  lightning-card  component attributes. Flow graphical preview improvements and fixes, round two Replaced the  Show/Hide Details  toggle toolbar button with a more extensive  Flow Diagram Settings  toolbar button. Settings are configured at the  IDE level  by default but can also be configured at the  project level  if desired. When configured at the project level, settings are stored in  .idea/illuminatedCloud.xml  and can be safely stored and shared through version control. The following settings can now be configured to control Fl...

  2.2.9.5 Issue 2476  - Prospective performance improvement when deploying via the metadata API in very large projects with Local Files subscriptions. This still doesn't resolve slow times discovering the metadata types/names of all files in large projects, but it should help with deployment specifically. Realistically, projects with extremely large numbers of metadata objects (in the reported case, >100K local metadata files) should use a Package.xml-based metadata subscription. Fixed an issue with automatic module problem resolution as the project is opening. Flow graphical preview improvements and fixes Issue 2483  - Fixed a broad class of potential NPEs that could occur when Flow XML elements that were previously expected to be present (based on my limited access to test Flow metadata) were not in fact present. Symbolic details are now presented in a fixed-width (i.e.,  code ) font. Added numeric indices on filters so that custom filter logic references are pr...