2.3.4.8 release notes

2.3.4.8

  • Issue 2727 - Spring '25 / API v63.0 update completion

    It looks like the last instances have been updated to Spring '25 / API v63.0, so this build includes updates for the SOAP and REST API clients to communicate using that version. If you see errors like UNSUPPORTED_API_VERSION, please revert to the previous release and let me know your org and instance IDs.

    This build includes the following Spring '25 / API v63.0 changes:

    • Updated the SOAP client for API v63.0.
    • Updated the API version used for primary communication with Salesforce APIs to 63.0.
    • Updated metadata.xsd based on the API v63.0 Metadata API SOAP WSDL.
    • Updated the OST version number to prompt regeneration for system API changes in API v63.0.

  • Issue 2716 - Integrated the SLDS Validator static code analyzer into IC. This is considered a beta-level feature due to the known issues described below. A demonstration video is available here.

    The SLDS Validator is delivered as a language server, so this integration requires LSP4IJ. The entry point for the integration is a new code inspection, Settings | Editor | Inspections | Salesforce | SLDS Validator, that helps to install LSP4IJ and download/register the SLDS Validator language server distribution.

    Once installed, the SLDS Validator will report issues and suggestions for Aura and LWC markup, CSS, and JavaScript/TypeScript files. Some issues and suggestions include quick fixes which are made available as context actions. IC also includes a context action, Suppress with 'sldsValidatorIgnoreNextLine' comment, which adds a suppression comment immediately before the declaration/statement/tag to which the reported issue or suggestion is attributed. IC also includes a new surround-with live template, ign, that surrounds the editor selection with sldsValidatorIgnore and sldsValidatorAllow comments (see below regarding issues with this mechanism).

    Note that I have found and reported a number of issues with the SLDS Validator language server — some quite serious — including the following:
    • 141 and 144 - There are issues with the file position values specified for diagnostics and, more importantly, edits to be applied by code fixes.
    • 142 - sldsValidatorAllow doesn't seem to resume static code analysis properly. I suggest just using sldsValidatorIgnoreNextLine until this is fixed.
    • 143 - Some issues are still reported after applying the suggested quick fix. I suggest getting the code into the desired state and then suppress any remaining false positive using the Suppress with 'sldsValidatorIgnoreNextLine' comment context action.

    At present, it is not possible to configure the SLDS Validator aside from the language server jar location and whether or not it is enabled via the SLDS Validator code inspection. If I find a way to configure the static code analyzer behavior in a more discrete fashion similar to PMD rulesets, I will enhance this integration to include such configuration.

  • Issue 2730 - Enhanced the Apex Annotation and Modifier Agreement code inspection to detect and report method and constructor declaration signatures with return types and/or parameter types that are inaccessible from valid callers of the method/constructor. The inspection includes quick fixes to change the return/parameter type visibility to match the method/constructor visibility and vice-versa.

    These issues are reported as warnings because technically such declarations are allowed by the Apex compiler, though usages of them via the higher-visibility method/constructor interface will result in compilation failures.