Illuminated Cloud Announcements

  2.2.4.9 JetBrains 2022.3  - Compatibility updates for the JetBrains 2022.3 base IDE releases.

  2.2.4.8 Issue 2251  - I finally figured out how to open selected metadata in the Lightning setup UI instead of (or rather, in addition to) the Classic setup UI. The  Open in Salesforce Setup  action has been split into  Open in Salesforce Lightning Setup  and  Open in Salesforce Classic Setup  actions with the keyboard shortcut associated with the  former  by default, though that can be changed in the active keymap if desired. Note that there are  many  more one-off URL exceptions in the Lightning setup UI, so if you see a local metadata file that opens incorrectly or fails to open at all but should, please file a bug in the public issue tracker and I'll be happy to address it. Please be sure to include the specific metadata type and exactly where it should open in the Lightning setup UI as that's not always obvious. Issue 2252  - Fixed an issue with hiding  meta.xml  files in alternate  Project  view...

  2.2.4.7 Issue 2240  - When scratch org creation fails, the user is now prompted to reopen the scratch org creation dialog with the exact same settings so that the reported issue(s) can be corrected and the creation retried. Issue 2244  - Fixed an issue with the resolution of inherited inner types more than a single level of inheritance "away" from the point of usage. Issue 2246  - Fixed a few SOQL issues: The argument for  GROUPING  should now be handled properly as a qualified field name. Specialized completion insert handlers should now behave properly in standalone SOQL queries, i.e., those in the  SOQL Query  tool window and in  .soql  files. WITH SECURITY_ENFORCED  and  ALL ROWS  clauses are now flagged as invalid in standalone SOQL queries as they're only allowed in Apex query expressions. Issue 2247  - Fixed a regression from the recent constructor improvements where an implicit constructor, either the defaul...

  2.2.4.6  - Hotfix for  2.2.4.5 Issue 2245  - Fixed an issue with the new project wizard for metadata format projects where the full list of metadata would not be shown properly in the subscription editor once a connection is selected. This was an accidental regression introduced as a side effect of the new  .forceignore  file support in 2.2.4.5.

  2.2.4.5 Issue 1066  - Deployments which include Apex classes that implement the  System.Schedulable  interface will now automatically use the Metadata API to work around an issue with Tooling API-based deployment of such classes when already scheduled. Issues 2195 and 2215  - Added full support for  .forceignore  files in source format projects including: First-class file type for  .forceignore  files with syntax highlighting, code completion, entry validation, (limited) reference navigation, etc. File status highlighting of ignored files in the IDE's  Project  view. Filtering of ignored metadata types and objects in the build options dialog and metadata subscription editor. Add to .forceignore  actions in the  Illuminated Cloud  drop-down and context menus, build options dialog, and metadata subscription editor. A  .forceignore  file is created if not already present in the project root directory. Add to ...