2.3.6.0 release notes

2.3.6.0

  • Issue 2784 - API-based deployment is now disabled/bypassed when sfdx-project.json includes string replacement configuration. Note that IC doesn't try to determine whether or not the specific files requested for deployment would have string replacements based on that configuration. If any string replacement configuration is present in sfdx-project.json, all deployments are performed using the Salesforce CLI.
  • Issue 2786 - Improved the behavior when creating or executing a Salesforce API-specific HTTP client request and invalid connections are present.
  • Issue 2793 - Added a few missing PMD distribution jars to the PMD Salesforce inspection's runtime classpath.
  • Issue 2794 - Fixed an incorrect utility method import that could result in incomplete generation of .illuminatedCloud/lwc/types module type definition files when LSP4IJ was not installed and enabled.
  • Implemented several small enhancements for the new Salesforce Code Analyzer integration:
    • Added a new inspection configuration option, External annotator | Maximum wait time, that determines the maximum amount of time in seconds that the external annotator should wait for the Salesforce Code Analyzer CLI command to complete. The default value is 15 seconds, and the allowed range is 10-30 seconds.
    • Added a new inspection configuration option, Agentforce for Developers quick fix | Maximum context length, that determines the maximum length in bytes of the surrounding declaration context that will be submitted in the Agentforce for Developers prompt for rules that benefit from more extensive context, e.g., pmd.FieldDeclarationsShouldBeAtStart. Higher values can yield better responses but can also result in longer prompt execution times or even failures. The default value is 7.5K, and the allowed range is 5K-30K.
    • The bulk inspection now only considers deployable source files when computing a common root directory for which Salesforce Code Analyzer should be executed. This can help ensure that project-level execution is rooted at, for example, force-app/main or src instead of the project root directory which can often contain large numbers of irrelevant files, potentially slowing down execution. Note that known configuration directories, e.g., config and manifest, and resource-type source roots are not considered deployable source roots. Explicitly excluded directories are also taken into account when computing a common root directory for execution.
  • Implemented several optimizations to the generation of .illuminatedCloud/lwc/types LWC module type definition files, specifically to avoid the need for index-based information since indexing can often be occurring when these files are being generated.
  • Added support for distinct highlighting of USER_DEBUG log entries based on their logging levels. This is most evident in the Anonymous Apex and Log Analyzer tool windows, and, while enabled by default, it can be disabled easily via those views if desired.

    Highlighting styles can be configured in Settings | Editor | Color Scheme | Console Colors with the following mappings:
    • LogLevel.NONE ⇒ Console | Standard output
    • LogLevel.INTERNAL ⇒ Console | System output
    • LogLevel.FINE ⇒ Log console | Verbose
    • LogLevel.FINER ⇒ Log console | Verbose first-level derivative
    • LogLevel.FINEST ⇒ Log console | Verbose second-level derivative
    • LogLevel.DEBUG ⇒ Log console | Debug
    • LogLevel.INFO ⇒ Log console | Info
    • LogLevel.WARN ⇒ Log console | Warning
    • LogLevel.ERROR ⇒ Log console | Error