Illuminated Cloud Announcements

2.3.8.5 Implemented several enhancements and fixes for the GraphQL support features added in  2.3.8.4 : Issue 2865  - Addressed numerous gaps in the SOQL-to-GraphQL query conversion logic: Added conversion of all known supported SOQL functions and aggregates in  ORDER BY  and  GROUP BY  clauses including the  DISTANCE()  and  GEOLOCATION()  functions. Note that these two specific functions are  not  supported in GraphQL in the  SELECT  clause (at least as far as I can tell) and are emitted as a comment if found in that clause in the source SOQL query. Added conversion of the SOQL  GROUP BY CUBE  and  GROUP BY ROLLUP  clauses. Added conversion of the SOQL  LIMIT  clause into the corresponding GraphQL  first  clause. Added conversion of the SOQL  FOR REFERENCE/VIEW  clauses into the corresponding GraphQL  updateMRU: true  clause. Added conversion of polymorphic...

2.3.8.4 Added full support for Salesforce GraphQL queries in both commercial and free JetBrains IDEs. A  demonstration  is available for all features described below. Issue 2467  - General Salesforce GraphQL support features including: Help installing, enabling, and configuring the  JetBrains GraphQL plugin . Quick fix to retrieve and register the org-specific GraphQL schema so that code completion, validation, etc., work properly in Salesforce GraphQL queries. When the GraphQL schema is retrieved, IC can also include a default project configuration in the resulting  graphql.config.yml  file for the project's configured connection so that the GraphQL plugin can execute Salesforce GraphQL queries directly against the org. Note that this does require the connection's access token/session ID to be added to  graphql.config.yml , but if that's a concern, it can be disabled as  Illuminated Cloud | Configure Application | GraphQL | Configuration Manageme...

2.3.8.3 Reissue of  2.3.8.2  with a hotfix for an issue with LWC template braced expressions for event handler attributes. Issue 2868  - Improved filtering of LWC attributes displayed for code completion and integrated component documentation so that only public,  @api -decorated, writable fields/properties are included. If you find that something is no longer included that should be, please provide a concrete example and I'll be happy to address the omission. Issue 2869  - Fixed an issue with generation of  .illuminatedCloud/lwc/types  definitions when there are multiple metadata files with the same name, e.g., multiple  CustomLabels.labels-meta.xml  files. Issue 2870  - Fixed an issue where cross-metadata references could be added incorrectly for SObject fields with the same name in another SObject type. Issue 2873  - Fixed return types of  reportValidity()  methods and fixed names of  setCustomValidityForField() ...

2.3.8.2 Issue 2868  - Improved filtering of LWC attributes displayed for code completion and integrated component documentation so that only public,  @api -decorated, writable fields/properties are included. If you find that something is no longer included that should be, please provide a concrete example and I'll be happy to address the omission. Issue 2869  - Fixed an issue with generation of  .illuminatedCloud/lwc/types  definitions when there are multiple metadata files with the same name, e.g., multiple  CustomLabels.labels-meta.xml  files. Issue 2870  - Fixed an issue where cross-metadata references could be added incorrectly for SObject fields with the same name in another SObject type. Issue 2873  - Fixed return types of  reportValidity()  methods and fixed names of  setCustomValidityForField()  methods of several standard LWC components. 

2.3.8.1 Issue 2858  - Winter '26 / API v65.0 update additional items Updated the SOAP client for API v65.0. Updated  metadata.xsd  based on the API v65.0 Metadata API SOAP WSDL. Added stub definitions for the  LWC state management API . These are  very  simple stubs that will be expanded into complete signature definitions once the APIs are better documented. Issue 2871  - The prospective fix for duplicate path segments in metadata files retrieved via the Salesforce CLI from  2.3.8.0  had issues, so this build includes what I'm hoping is a more complete and reliable workaround/fix.

2.3.8.0 Reissue of  2.3.7.9  with a hotfix for a potential NPE during retrieve-for-merge that I observed when testing something else almost immediately after release. Issue 2864  - Implemented a performance optimization during post-retrieve metadata files population so that bundles are only reconciled once per-bundle directory instead of once per-bundle content file. Fixed an issue with metadata subscription management where placeholder  *.object-meta.xml  files would be processed incorrectly resulting in the entire SObject type being added to the subscription when only children of that type are actually subscribed. Added warnings to indicate clearly that native connections should now be considered deprecated and will  no longer be supported  starting in Summer '27. IC will continue to support native connections as long as the underlying API is still available, but users are  strongly encouraged  to migrate from native connections to  OA...

2.3.7.9 Issue 2864  - Implemented a performance optimization during post-retrieve metadata files population so that bundles are only reconciled once per-bundle directory instead of once per-bundle content file. Fixed an issue with metadata subscription management where placeholder  *.object-meta.xml  files would be processed incorrectly resulting in the entire SObject type being added to the subscription when only children of that type are actually subscribed. Added warnings to indicate clearly that native connections should now be considered deprecated and will  no longer be supported  starting in Summer '27. IC will continue to support native connections as long as the underlying API is still available, but users are  strongly encouraged  to migrate from native connections to  OAuth connections  to ensure seamless continued support. Implemented a workaround for a Salesforce CLI issue that could result in the paths of newly-retrieved metadat...