2.2.6.2 release notes
2.2.6.2
- Updated the IcApexDoc integration to support the new ApexDoc validation feature added in 1.0.0.3. This integration includes the following features:
- You can choose to use the ApexDoc validation code inspection settings as the validator options for consistency between the two tools. This is the default behavior if the ApexDoc validation code inspection is enabled for the project's inspection profile.
- Alternatively, you can select an IcApexDoc validator options JSON file to be used when running IcApexDoc. If unspecified and code inspection settings are not used, the default validation configuration is used.
- Added a JSON schema for IcApexDoc validator options JSON files, specifically those named
apexdoc*validator*.json, that provides code completion and validation when IC2 is used with any supported commercial JetBrains IDE. - If IcApexDoc executes successfully with validation warnings, you can choose to have the Messages tool window containing the full execution output opened immediately where all validation warnings are automatically hyperlinked to the respective source code.
- Fixed a few small issues in the ApexDoc validation code inspection discovered while implementing the corresponding validation features in IcApexDoc.
- Addressed a rare corner case where indexing wouldn't necessary occur in a 100% consistent and correct order after large-scale changes, e.g., OST generation, potentially resulting in transient stale or broken inheritance relationship references.
- After using 2023.1 comfortably for a while, I've increased the recommended host JetBrains IDE version to that. Note that this is a soft constraint and JetBrains IDE versions 2022.1.4-2023.1 are all supported by IC2.