2.3.7.2 release notes

2.3.7.2

• Issue 2815 (progress) - Added more cross-metadata references, specifically for those to non-decomposed child metadata in metadata format projects, e.g., custom fields in *.object files. As stated previously, I'll continue to chisel away at this gradually across upcoming builds until I feel I've covered what I can.
• Issue 2823 - IC now verifies that the module's configured default source root matches the specified default package directory in sfdx-project.json in modules/projects with multiple source roots. A module resolution fix is provided to update the default source root to match the default package directory if different.
• Issue 2827 - Fixed an issue where violations reported by Salesforce Code Analyzer in files without first-class language support could be incorrectly attributed at the file-level instead of at the reported location.
• Issue 2830 - Fixed an issue where the user could be prompted about deployment of unsubscribed metadata when saving a file not under a source root when tabbed editors are enabled.
• Issue 2831 - Fixed an issue with dynamic static resource file type association for files with extensions that are associated with known IDE files types.
• Issue 2833 - Added properties derived from @AuraEnabled Apex instance getter methods to generated stubs under .illuminatedCloud/lwc/types/apex.
• Issue 2834 - Added the disable-animation attribute to the LWC lightning-button component. Note that this attribute is documented as "Reserved for internal use", but it's also used in the component documentation for its animation behavior. In general, though, "Reserved for internal use" attributes are not included in IC's bundled component definitions.
• Updated integrated API documentation for Apex, Visualforce, Aura, and LWC to match the latest IDE styles and organization.
• Fixed an issue with how IC evaluates the installed version of LSP4IJ for enabling conditional behavior.