2.3.9.6 release notes

2.3.9.6

• Issue 2922 (partial) - Implemented a few more fixes for PsiInvalidElementAccessException instances that I observed in my own work. I'll continue to try to track down the root cause of these invalid elements, but minimally I'm trying to be defensive against their presence and allow for recovery when possible.
• Issue 2925 - Corrected the data type of ConnectApi.CdpQueryOutputV2.metadata. Note that the OST must be regenerated to see the effects of this change.
• Issue 2926 - Made IC's file type overriders — used for metadata files with a single extension but multiple MIME types, e.g., static resources, content assets, email templates, and documents — much more selective about files for which they try to determine a file type. All files must pass the following gates:
  • Must be under a configured, deployable source root. Resource roots are not considered source roots for this check.
  • Must be in an IC module/project.
  Additionally the file types that are dynamic in metadata format projects but not source format projects, specifically static resources and documents, are not evaluated at all for files in source format projects. Hopefully this addresses issues with IC trying to apply dynamic file type logic to non-Salesforce files with intersecting extensions, e.g., *.resource for Robot Framework.
• Fixed an Agentforce for Developers regression due to a change in the API endpoint. Please let me know if you continue to see any issues with A4D functionality in IC.
• The Apex Annotation and Modifier Agreement inspection now properly flags classes with @IsTest and abstract/virtual as invalid with quick fixes to remove the annotation or modifier.