2.1.9.8 release notes
2.1.9.8
- JetBrains 2021.3 update status - It pains me to have to include another entry of this form in the change notes, but as you may or may not have already seen, the JetBrains 2021.3 updates were released earlier this week, and once again they create compatibility problems with IC2 (and many other plugins). I'm posting updates to issue 2015 if you're interested in monitoring the status, but JetBrains is fully-aware of the issue and should (hopefully) be issuing patches for the affected IDEs shortly. Once that has happened and I've confirmed that things look good, I'll post an IC2 update to unlock compatibility with 2021.3. Until then please remain on either 2021.1.3 or 2021.2.3.
- Issue 2007 - Implemented a fast tree expansion optimization in the SOQL Query result tree view that should help considerably when rendering larger result sets, even those which do not include child relationship data.
- Issue 2012 - In 2.1.9.7, several new Apex color scheme options were added including Parameters > Type parameter. This option is generally intended to control styling of generic type parameters in languages which support them, but in Apex it was being applied to the concrete type parameters used to parameterize the few Apex system types which allow type parameters. That option is still present, but now instead of defaulting to Parameter it instead defaults to Identifier. This will allow users to configure the color scheme for concrete type parameters without picking up the higher-level configuration for generic type parameters used by other languages.
- Implemented several changes to the way that PMD violations are reported via the PMD Apex and Visualforce code inspection:
- The inspection now includes several configuration options for which information is included in the reported violation. The default configuration yields a smaller subset of the information than has been previously included, but because it's configurable, the user is of course free to restore it to the same information as before if desired. The new configuration options are:
- Rule name - defaults to enabled
- Rule set name - defaults to enabled
- Rule priority - defaults to disabled as the code inspection already reports the issue at the corresponding severity
- Rule description - defaults to disabled as the description text can be quite verbose for what should be a succinct error report, and the description text is easily accessible via contextual code intention
- Rule external info URL - defaults to disabled as the rule external info page is easily accessible via contextual code intention
- The Markdown-to-HTML rule description transformation has been improved.
- Fixed an error that could occur when the Markdown plugin is not enabled.
- The inspection now includes several configuration options for which information is included in the reported violation. The default configuration yields a smaller subset of the information than has been previously included, but because it's configurable, the user is of course free to restore it to the same information as before if desired. The new configuration options are:
- Fixed an issue with LWC component names used as CSS names in JavaScript string literals not resolving properly and not providing proper code completion of known LWC component names.
- Evidently fields of type
ADDRESS
should be modeled in Apex asSystem.Address
and notSchema.Address
. Now they are rendered as such in the OST. Note that the OST must be regenerated to see the effect of this change. - Added Expand All/Collapse All toolbar buttons to the SOQL Query results tree view.
- Improved release notes tooltip presentation so that more of the original formatting is retained.
- Other related fixes and improvements.