2.3.6.4 release notes

2.3.6.4

• Added support for multiple context files in the Agentforce for Developers Dev Assistant tool window. The Use the selected editor option is still used to add the file in the selected editor tab as a context file, and there is now an Additional context files expandable text field and companion Add context file button to add and manage other files from the project that should be included in the generated prompt for context. Note that the Agentforce API does limit the prompt size, so adding large numbers of context files and/or large context files may result in errors during prompt execution.
• Added support for ESLint integration in JetBrains Community Edition IDEs via LSP4IJ 0.14.3 (not yet released, but you can install a nightly build to play with it now) and Microsoft's ESLint language server:
  • If ESLint is integrated via LSP4IJ and the Salesforce Code Analyzer 5 integration is configured to ignore redundant rules, Code Analyzer's ESLint engine is automatically disabled and ESLint results are provided in real-time by the language server. As always, it's important that both ESLint integrations use the same configuration. Note that this only applies for the external annotator. Code Analyzer's ESLint engine is still enabled when executed for a bulk inspection run because the pull diagnostics feature required for bulk analysis is not yet supported.
  • Added automatic upgrade logic for IC's generated eslint.config.mjs files to fix some issues observed by this ESLint language server integration in Community Edition IDEs, specifically adding Node types ubiquitously instead of just at the Jest test-level. Note that this upgrade logic will only be performed if the original eslint.config.mjs files are found in a (mostly) unmodified form.
  • NOTE: If you are still seeing false positives from ESLint, make sure that you have run npm install and that your .eslintrc.json and/or eslint.config.mjs files are properly configured including the following specific considerations:
    • For .eslintrc.json files under aura directories, make sure that the func-names and no-unused-expressions rules are set to off.
    • For .eslintrc.json files under lwc directories, make sure that env.node is set to true.
    • For eslint.config.mjs files under lwc directories, make sure that languageOptions.globals includes ...globals.node at the top-level.

NOTE: Version 2025.2 of all JetBrains IDEs will be available in the next few months or even weeks. Due to breaking changes in the 2025.2 plugin SDK, I will be dropping support for all 2024.* IDE versions when 2025.2 is released. I typically try to maintain compatibility with at least one full year of versions, e.g., as of the release of 2025.2, ideally 2024.3-2024.2, but in this case, I will need to remove support for 2024.3 one release cycle earlier than typical. To ensure a seamless upgrade path going forward, please make sure that you're using at least version 2025.1 of the underlying JetBrains IDE before 2025.2 is released. My sincere apologies for any inconveniences this may cause.