2.2.0.8 release notes
2.2.0.8
- Keyword/usage case configuration and management enhancements
- Added a new configuration tab to Settings / Preferences > Editor > Code Style > Apex, Case, for configuration of preferences for keyword case in case-insensitive languages such as Apex, SOQL, SOSL, and the Visualforce and Aura expression languages. For each language, case preferences can be selected for distinct token types, e.g., keywords vs. annotations vs. functions vs. constants/globals, as one of the following values:
- Recommended (default) - use Illuminated Cloud's recommended case, e.g.,
@IsTest. - Uppercase - use all uppercase, e.g.,
@ISTEST. - Lowercase - use all lowercase, e.g.,
@istest. - Capitalized - use leading uppercase followed by all lowercase, e.g.,
@Istest. - Camel case, leading upper - capitalize all words including the first word, e.g.,
@IsTest. - Camel case, leading lower - capitalize all but the first word, e.g.,
@isTest.
This tab also includes options to apply case corrections to tokens found with the incorrect case during code formatting. These options are disabled by default for backward compatibility.
- Recommended (default) - use Illuminated Cloud's recommended case, e.g.,
- Fixes and improvements to the ApexDoc code style settings tab and to the actual application of ApexDoc changes during code formatting when enabled.
- Added a new configuration tab to Settings / Preferences > Editor > Code Style > Apex, Case, for configuration of preferences for keyword case in case-insensitive languages such as Apex, SOQL, SOSL, and the Visualforce and Aura expression languages. For each language, case preferences can be selected for distinct token types, e.g., keywords vs. annotations vs. functions vs. constants/globals, as one of the following values:
- Quite a few other related fixes and improvements.