2.3.9.3 release notes

2.3.9.3

• Issue 2895 - Implemented a number of editor enhancements for Agent Script:
  • Added context-aware code completions and references for most internal relationships, e.g., variables, inputs, outputs, topics, utils, etc., and external relationships, e.g., Apex and Flow targets. Added references allow bidirectional navigation, i.e., go to declaration and find usages.
  • Improved completion insert handlers for certain token types, e.g., adding a space after the colon when inserting a standard label, and also removing the unnecessary trailing space if the user types Enter immediately to specify label data in a sub-block.
  • Added a new code inspection, Agent Script unresolvable reference, that flags unresolvable references in *.agent files as errors.
  • Added several missing Agent Script keywords and recategorized some tokens that were incorrectly categorized previously.
  • Added support for structure view in *.agent files.
  • Fixed issues with deployment error reporting for *.agent files. At present, these errors are not reported via the standard CLI error reporting channels, so IC processes the raw deployment failure to extract source file-attributed error details. It also seems that validation of *.agent files is only performed on the client side by the Salesforce CLI and not by the server itself, so while it's possible to deploy these files in a metadata format project, note that invalid files are deployed to the org without errors. As a result, I strongly recommend that Agent Script be used only in source format projects until validation is performed server-side.
  I've tried to implement a code formatter using the IDE's existing YAML formatter, but block instructions are not formatted properly and result in deployment failures. I may still try to get that working via a two-pass approach with the YAML formatter responsible for the first pass and IC adjusting block instructions explicitly as the second pass.
  This may not be 100% perfect, but until Salesforce's Agent Script language server is available, it should make for a much improved editor experience when working with *.agent files.
• Implemented several improvements in how IC identifies relationships between Apex test and tested classes. This is semi-related to issue 2912 as it lays some of the groundwork for the enhancement requested there, though it's not (yet) a direct response to that request.
• Added support for a few additional XML metadata reference types, specifically additional references to Apex classes from XML via apex://ClassName URLs as XML element values as well as XML attribute values which were already supported.
• Added a file type icon for Flow metadata files to make them more distinct as a first-class programming metadata type.