2.2.1.3 release notes

 2.2.1.3

  • Issue 2047 - Fixed issues with SOQL query code completion when selecting the Group SObject.
  • Issue 2052 - Fixed a number of issues with resolution of references to inner type declarations and their respective body declarations inside of Apex triggers. Also fixed several related issues with code completion, code generation, etc., in the same scenario.
  • Issue 2055 - Fixed an issue with inner type name resolution when the top-level type name is the same as a namespace, e.g., Functions.InnerTypeName. Previously IC2 would attempt to resolve this as InnerTypeName in the Functions namespace, but now it will properly resolve to the inner type if present.
  • Issue 2056 - Added a new Open in Salesforce Setup action to show the selected metadata file in the Salesforce setup Web UI. This action is available via the drop-down and context menus as well as via the keyboard using Ctrl+Alt+Shift+M (Windows/Linux) or Cmd+Opt+Shift+M (Mac). Note that most of the time the classic setup page is opened instead of the Lightning setup page as the common URL for showing an arbitrary metadata object defaults to classic. If anyone knows a generalized front door URL for showing the Lightning setup page for an arbitrary metadata object by ID, please let me know and I'll be happy to use it instead.
  • Issue 2067 - Added another known pattern for false errors reported when deploying LWC components via the Tooling API that will result in an automatic retry via the Metadata API. If more such patterns are found going forward, I may just have an automatic retry occur on any error reported as a FIELD_INTEGRITY_EXCEPTION during such deployments, but ideally this workaround would remain more focused and tactical.
  • Enhanced the Control Flow Analysis code inspection for break and continue statements:
    • Any break or continue statements found outside of loops are flagged as errors.
    • Any statements after break or continue statements are considered unreachable and are flagged as errors.
    • Any continue statements found as the last statement in a loop are unnecessary and are flagged as warnings.
    In all situations, a contextual quick fix is provided to remove the offending statement.
  • Enhanced the File Contents Verification code inspection to detect constructor names that do not match the enclosing class name. Full mismatches are flagged as errors, and case mismatches are flagged as warnings. Contextual quick fixes are provided to rename the constructor or enclosing class as appropriate.
  • Improved the File Contents Verification contextual quick fixes which result in declaration or file renaming such that all relevant rename logic is executed in response to the action.
  • Disabled all Apex code inspections for external Apex language injections. What this means is that if you use the language injection feature of the host JetBrains IDE with Apex code snippets not in Apex, Java, or JavaScript/TypeScript string literals, code inspection issues are no longer reported. This helps eliminate noise when using language injection for rich Apex authoring in XML values, CDATA blocks, and elsewhere.
  • Improved the presentation of integrated system API docs in quick documentation.
  • Other related fixes and improvements.