2.2.4.2 release notes

 2.2.4.2

  • Issue 2067 (redux) - Added another specific pattern of FIELD_INTEGRITY_EXCEPTION false deployment failure message when trying to deploy an LWC bundle file via the Tooling API such that IC2 will automatically retry the deployment via the Metadata API. Hopefully this further closes the window of opportunity for these types of false deployment errors, but if they continue to emerge I will likely need to make Tooling API-based LWC deployments that fail with a FIELD_INTEGRITY_EXCEPTION always retry using the Metadata API to provide a seamless experience.
  • Issue 2219 - Package.xml-based subscriptions are now handled properly in the new project wizard for metadata format projects. When that metadata subscription type is selected, a relative path of src/package.xml is used. The metadata selection tree contents are used to seed that file for the new project and any initial deployment and/or retrieval operations.
  • Issue 2223 - The String-based signatures of System.Database.getQueryLocator() were no longer being included in the Tooling API's completions?type=apex REST resource after the Winter '23 update even though they're still legitimate signatures, so I've restored them. This fix requires that the OST be regenerated.
  • The metadata subscription editor has been changed (hopefully improved) in a few ways:
    • The default subscription type in the new project wizard for metadata format projects is now Package.xml instead of Selected. This is only a change to the default to encourage the best practice of a subscription that can also be used outside of IC2, but Selected is of course still an available and valid option.
    • The Selected metadata subscription type is no longer visible in the subscription editor for a source format project/module.
    • The All/Package metadata subscription type is no longer visible in the new project wizard for metadata format projects, and is only visible in the module subscription editor if that module already uses an All/Package subscription and/or is configured for a development package such that the Package aspect of such a subscription would make sense without resulting in a full-org subscription. This is effectively an attempt to "soft remove" All/Package as an available metadata subscription type without penalizing those who already use it. I strongly recommend that those use do use it without a development package filter consider switching to a Package.xml or Selected metadata subscription to formalize the subset of org metadata included in the subscription to what is necessary for that project.
  • Constructors are now handled properly for Exception types. The standard constructor signatures are now offered for those types even if not explicitly declared, and the Unresolvable Signature code inspection now flags invalid usages of Exception constructor signatures.
  • Added support for comma-delimited type/member references in ApexDoc @see tags. This is a non-standard usage of the @see tag, but it seems to be used broadly enough to warrant support. Now IC2 supports @see values with either a comma-delimited list of type/member references without description text or a single type/member reference optionally with description text. This change also includes a new ApexDoc formatter option, One @see per-line, that, when enabled (default as that's the standard usage), formats:

    @see TypeNameWithDescription description text
    @see TypeName[.memberName], OtherTypeName[.otherMemberName], ...

    as:

    @see TypeNameWithDescription description text
    @see TypeName[.memberName]
    @see OtherTypeName[.otherMemberName]
    @see ...

    and, when disabled, does the opposite.
  • Added support for Visualforce and Aura components in the current namespace via the org namespace in addition to the local namespace prefix, e.g., <myNamespace:myComponentName .../> and <c:myComponentName .../> respectively. The latter is still the preferred way to reference local components, but the former is technically valid and is therefore now properly supported.