Illuminated Cloud Announcements

  2.2.6.0 JetBrains 2023.1 update  - Changes required for compatibility with JetBrains' 2023.1 IDE releases. Quality of life improvements Issue 2318  - Changed the way that IC2 determines whether or not a file is a source or SDK file so that it uses the IDE's native project file index. For the few who have experienced a deadlock on initial project startup, this should take care of it. For all users, this might result in a slight overall performance increase. Issue 2331  - The user is now prompted when closing Anonymous Apex and SOQL Query tool window tabs if the tab is unsaved and has contents or is saved and modified relative to the corresponding file. Issue 2333  - ApexDoc comments are no longer required to be on the line immediately preceding the documented declaration. There can now be any number of intermediate blank lines separating the comment and the declaration. Fixed a memory leak that would result in accumulated cached data as projects are closed across the lifetime

  2.2.5.9 Public issue tracker offline  - I wanted to make everyone aware that the public issue tracker for IC2 is currently  unavailable  due to a  broad spam attack on Bitbucket public issue trackers . As I posted in a recent  update , Atlassian/Bitbucket support is still requesting that affected issue trackers be kept private while they implement measures to mitigate the impact of this attack. In the meantime, please feel free to send any bug reports, enhancement requests, etc., directly to me via  email  or in the  public discussion groups . I have been transcribing these requests into the issue tracker so that they're concretely on my working backlog and available for community feedback once the issue tracker is restored to a public state. I appreciate your patience and understanding while this valuable resource is offline. Issue 1419  - The IDE's browser configuration is now used even for URLs opened via the Salesforce CLI. This allows the use of browsers that are not sup

A little shy of two weeks ago I posted that the IC2 public issue tracker has been changed to private temporarily due to a broad spam attack on Bitbucket Cloud public issue trackers including IC2's. As a quick update, I have been in active discussion with the Atlassian/Bitbucket Cloud support team (including engineers) who are actively working to address this problem, but as it continues to be a problem, they have recommended keeping affected issue trackers private until they say otherwise. In the interim, I have been conveying bugs and enhancement requests provided by users via email, public discussion groups, and even direct chat into the issue tracker so that they will be concretely on my working backlog for IC2 and available for broader group input once the issue tracker is restored to public status. My hope is that this is resolved very soon, but if it drags on too long, I'll likely look into some alternative host for a public issue tracker. Hopefully that won't be nec

Someone has decided to start a spam attack on a number of BitBucket-based public issue trackers. This started mid-day yesterday with a slow trickle of spam-type new issues, but overnight the pace increased to a point where I'll be spending quite a bit of the morning cleaning up spam issues. Unfortunately the only mitigation is to change the issue tracker from public to private. I have contacted BitBucket about this but haven't yet received any useful response. I am currently investigating options for a new public issue tracker that can be used to log bugs, enhancement requests, etc. In the interim, feel free to use support@illuminatedcloud.com  to report issues. I apologize for the temporary inconvenience. I will report any further updates here as they become available.

  2.2.5.8 ApexDoc Enhancements Integrated  IcApexDoc  for generation of project- or module-wide API documentation. IcApexDoc must be available on the local system, ideally with the main script available through the system execution path. You can then generate documentation using the new  Generate ApexDoc...  action from the toolbar, drop-down menu, or context menu. The following settings can be configured for the tool and are retained across invocations: Executable  (required) - the path to the  apexdoc  executable; automatically populated if available via the system execution path; provides a download link if not already available locally. Scope  - the scope for which documentation should be generated, either  Project  or  Module ; note that this option is only displayed for multi-module projects where all modules are metadata format; otherwise  Module  scope is used. Output directory  (required) - the path to the directory in which documentation files should be generated. Exclude fil

You may have noticed that there were no Illuminated Cloud 2 updates last week or this week. That's not due to a lack of progress, but rather because I decided to spend a little time working on a derivative work for both Illuminated Cloud 2 users and the broader Salesforce development community. Today I've released IcApexDoc , a command-line HTML documentation generator for Salesforce projects. IcApexDoc is freely available under the Apache 2.0 license , initially as a binary distribution, but I'm planning on an open source offering in the near future. I've also posted a demo video of the tool's usage and features. Now that IcApexDoc has been released, I intend to integrate it very tightly into Illuminated Cloud 2 alongside the existing ApexDoc authoring features. This integration will facilitate generation of project-level HTML documentation for internal use or even for delivery to external consumers such as partners and customers. If all goes well, it should be i