Illuminated Cloud Announcements

  2.2.6.4 Issue 2290  - Significantly overhauled the way that reported deployment errors are presented to the user in both the  Illuminated Cloud > Problems  view and the  Messages  view: Reported errors are partitioned into three categories: Failures  - Standard failures that are typically directly attributable to the metadata/source file that raised the error. Transitive failures  - Failures in a metadata/source file that are the result of a failure elsewhere, e.g.,  ClassA  references  ClassB  which references  ClassC  which contains a syntax error. Transitive failures are resolved when the underlying root cause failures are addressed. Whenever possible, transitive failures are hyperlinked to the associated root cause. Unexpected errors  - Affectionately known as  GACKs , these are Salesforce internal server errors with very little actionable diagnostic information. Resolving the standard failures will...

  2.2.6.3 Issue 2325  - Added an option to the  Safe navigation operator usage  code inspection for whether to warn about usages of the safe navigation operator in operands of relational expressions. While such usages are technically valid, they can result in confusion. This new option is  enabled by default , so the inspection will continue to yield the same results as before, but if desired, those specific warnings can now be disabled via either the code inspection settings directly or via contextual intention/quick fix for a warning against a relational expression operand. Issue 2336  -  Inconsistent API version  code inspection banner messages now take the IDE project frame width into consideration and use abbreviated messages for narrower frames. Issue 2338  - Fixed an issue with CLI-based deployment that would result in  No authorization information found for -g  due to a  regression  in the Salesforce CLI's  fo...

  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 ...

  2.2.6.1 IcApexDoc integration improvements Updated the  IcApexDoc  integration to support all new options added in  1.0.0.2 : IcApexDoc command-line options can now be read from an options file. ApexDoc can now be generated for a namespace, either specified in the project's  sfdx-project.json  file or explicitly as a command-line argument. Alternatively, if the  sfdx-project.json  file specifies a namespace that should not be used, IcApexDoc can be instructed to ignore it. Org-only Apex types can be retrieved and included in the IcApexDoc run alongside local and standard Apex types so that inheritance relationships from local Apex types to org-only types are properly reflected in the generated ApexDoc. Retrieved org-only Apex types can also be included in the generated ApexDoc if desired. The parent directory of the  sfdx  executable used by IC2 is now explicitly added to the beginning of the  PATH  environment variable befor...

Just under a month ago, many of the Bitbucket Cloud public issue trackers--including IC2's--were the target of a broad spam attack . In response, I changed the IC2 issue tracker from public to private and have kept it that way  ever since per-guidance from Atlassian/Bitbucket support. Today I'm testing the waters by moving it back to public, though the change may be short-lived if I see any new signs of an attack. It looks like there are at least some new features for management of spam issues, and I know Bitbucket is working on a more comprehensive solution to this problem. Again, if I begin to see even a trickle of new spam issues, I'll revert the issue tracker to a private state until Bitbucket support gives the all-clear. Hopefully that won't be necessary, though.

Earlier today I posted about a multi-day outage with the licensing servers used by Illuminated Cloud 2. As of about an hour ago, service seems to have been restored. All pending orders should now have completed, all renewed subscriptions should have been properly extended, and the license management self-service features should again be available. If you do see any further issues with ordering, license management, etc., please let me know ASAP. Again, apologies for the inconvenience caused by this outage.

The licensing software used by Illuminated Cloud is currently experiencing an effective outage.  The outage seems to have started on Friday, March 31, 2023 at approximately 10AM CDT. The vendor is aware of the issue and is actively working to restore service for all clients. Until then, the following Illuminated Cloud 2 services are affected: New order fulfillment - All new orders in FastSpring become stalled in during license key generation. Once the service is restored, these orders will complete and license keys will be issued. I am actively contacting those with orders in this state to let them know what's going on, and I'm offering trial extensions to cover the time until their orders complete. Existing subscription renewal - License key expiration dates are not being updated automatically upon succcessful subscription renewal in FastSpring. I am manually updating expiration dates, but there may be a slight delay before license expiration dates are updated. License manag...