2.3.5.0 release notes

2.3.5.0

• Issue 2732 - Since updating to version 2024.3+ of your JetBrains IDE, you may have seen messages like "'Illuminated Cloud 2' might be slowing things down". This is a new message added by JetBrains to help identify behaviors in plugins — both first-party and third-party — that are not properly offloading long(-ish)-running behaviors to background threads. This doesn't mean that anything that has actually changed for the worse in IC (or whatever plugin/subsystem you might see attributed with this message). It just means that less-than-ideal existing behaviors are now being reported to help identify and resolve them.
  
  In this build, I've refactored IC's main long-running operations — metadata deployment, retrieval, and removal; offline symbol table generation; Salesforce CLI execution; anonymous Apex and SOQL query execution; etc. — so that they are moved to a background thread and, if appropriate, a progress indicator as quickly as possible after being invoked. Additionally, nested long-running behaviors should now properly share progress indicators so that an existing background process should no longer result in a transient modal progress dialog, and overall progress of composite long-running operations should now be reported more accurately.
  
  While I've tested them extensively via both automated regression testing and manual smoke testing, there is still a distinct possibility of regression from such a broad class of changes. If you find that something that previously executed properly in the background no longer does, or worse, you find that some operation now fails, please accept my apologies in advance and report the specific regression to me so that I can turn around a hotfix for it ASAP. Hopefully, though, you will find that these types of operations now start faster, report progress more accurately, and overall stay out of your way better while they execute.
• Issue 2738 - Partial fix for resolution of ambiguous unqualified type name Location which can be either System.Location or Schema.Location. IC attempts to infer the correct type from the declaration's initializer expression, and if missing, the declaration is assumed to be System.Location. This appears to be slightly different from how the Apex compiler infers this type, though, so it may not be a perfect solution for your usages. I hate to say it, but if/when IC still seems to be inferring the wrong Location type, please add an explicit namespace qualification and provide a concrete example so that I can further amend this type disambiguation logic.
• Issue 2746 - Fixed an issue that could occur when pasting incomplete/syntactically incorrect Apex code.
• Issue 2748 - Prospective fix for an issue with how modules are identified for files in multi-module projects with overlapping content roots.
• Fixed an issue where focus would transfer to the Messages tool window after a background operation completes when the Messages tool window is showing at the time. This could specifically have caused an interruption in typing flow after completion of deploy-on-save.
• Prospective fix for an issue with the IDE's static code analyzer never completing for some TypeScript files in non-IC projects. If you've been having this issue, I recommend using File | Invalidate Caches... | Invalidate and Restart in projects with the issue after installing this build to force a full cache/index rebuild.
• Other related under-the-hood fixes and improvements.