2.0.7.8 release notes

posted by Scott Wells

2.0.7.8

  • Issue 1344 - The correct tab should be displayed in tabbed editors when debugging JavaScript via Jest, opening search results, etc. This isn't a perfect solution, but given the limitations of the plugin SDK around multi-tabbed editors, it's probably as close as it's going to get until first-class support is available.
  • Issue 1372 - Added debug level and trace flag configuration to Illuminated Cloud. From Log Analyzer, select the connection for which configuration should occur and click the Configure Logging toolbar button to open the configuration dialog:
    • Debug levels
      • Add, edit, and remove named debug levels.
      • Use log level presets to configure debug levels for debugging or profiling.
      • NOTE: The special SFDC_DevConsole debug level cannot be deleted or renamed, but its log levels can be configured.
    • Trace flags
      • Add, edit, and remove trace flags. User-defined trace flags can be created for users or Apex classes and triggers.
      • Set the effective period for each trace flag via the start date (optional) and expiration date.
      • Easily refresh or remove expired trace flags using the respective toolbar buttons.
    NOTE: Changes to debug levels and trace flags are not committed to Salesforce until the dialog is dismissed with the Save button. Pending changes can be discarded using the Cancel button.
  • Other fixes and improvements.

2.0.7.7 release notes

posted Aug 15, 2019, 8:00 AM by Scott Wells

2.0.7.7

  • Issue 1356 - IC now automatically helps exclude the .sfdx/tools/sobjects directory if present to prevent resolution against SObject stub classes found there which don't extend SObject properly.
  • Issue 1382 - Fixed an issue that could cause IC to lose module/connection associations in projects where multiple modules share the same connection.
  • Issue 1387 - Added a Debug Only view configuration for the Log Analyzer hierarchical view.
  • Improvements when deploying unsubscribed metadata:
    • The prompt is now only shown during deploy-on-save actions since bulk deployment actions originate in the metadata selection screen and any unsubscribed metadata is likely intentional.
    • The prompt is now shown properly when deploying via the Tooling API. Previously it was only shown when deploying via the Metadata API.
    • The prompt is no longer shown when deploying a CustomLabels file while subscribed to specific CustomLabel metadata.
  • Fixed an issue that could occur when trying to configure application settings with a completely unconfigured native connection.
  • Added the Apply action to the Configure Application/Project/Module dialogs.
  • Improved handling of malformed local SObject XML files during OST generation.
  • Other fixes and improvements.

2.0.7.6 release notes

posted Aug 9, 2019, 7:13 AM by Scott Wells

2.0.7.6

  • Issue 1377 - Added Mine_And_My_Groups as a valid option for SOQL's USING SCOPE clause.
  • Issue 1386 - The proper host IDE name is now used instead of "IDEA" or "IntelliJ IDEA".
  • Fixed an issue with the new Log Analyzer that could result in the raw log body not being displayed intermittently.
  • Fixed an issue with retrieval of decomposed metadata in a Salesforce DX-develop-against-any-org module where retrieved child metadata files with ambiguous names, e.g., fields with the same name across multiple objects, could be matched to the wrong local child metadata file.
  • Retrieved decomposed metadata is is also now matched more accurately against existing directory structures for the same decomposed metadata, e.g., retrieving a new field for a previously-retrieved object.
  • Partially restored language injection for single string literal regular expressions only. Concatenated string literal injection and dynamic SOQL string literal injection will be restored when JetBrains addresses IDEA-220176.

1.8.5.3 release notes

posted Aug 9, 2019, 7:11 AM by Scott Wells

1.8.5.3

  • Issue 1362 - Added support for IntelliJ IDEA 2019.2 when running in a Java 11 JRE. Note that this adds a new plugin build specific to 2019.2+ that bundles JAX-WS. Builds for previous versions should be unchanged except that IlluminatedCloud-14.zip now supports IntelliJ IDEA 14-2019.1, and IlluminatedCloud-19.zip supports IntelliJ IDEA 2019.2 and higher.

2.0.7.5 release notes

posted Aug 6, 2019, 12:14 PM by Scott Wells

2.0.7.5

  • Issue 1379 - Fixed an issue that occurred for (at least) one user where the log operation was returned as a numeric value instead of a string value.
  • Issue 1380 - Fixed an NPE that could occur when trying to execute anonymous Apex without first selecting a log level preset.
  • Issue 1381 - Adjusted the log level configuration panel layout so that it fits properly on lower resolution screens. Screens down to 1366 px width should be fine in all cases; screens with 1280 px width are fine in Log Analyzer and Anonymous Apex but are still slightly truncated in Apex unit test and offline debugger run configuration dialogs. Getting things working on those screens will require a larger layout change, so I'd be curious to hear from folks working on such screens.
  • Fixed an issue that was preventing new SFDX project creation in some situations.
  • Fixed an issue that occurred during metadata retrieval when there are multiple source roots and just confirming the module configuration dialog doesn't save the default source root.

2.0.7.4 release notes

posted Aug 2, 2019, 7:22 AM by Scott Wells

2.0.7.4

  • Issue 931 - Log Viewer is now Log Analyzer, a full-featured log analysis and profiling tool:
    • Added a new hierarchical view for debug logs.
      • You can easily switch between the raw and hierarchical views using the corresponding tabs at the bottom. The last selected view is retained across sessions.
      • By default the corresponding source location is opened as you browse the hierarchical view of a log. This can be enabled or disabled using the Autoscroll to Source option of the hierarchical view. You can also access the associated source by double-clicking any row in the hierarchical view corresponding to a local source file.
      • You can now maximize the viewed log to provide more real estate for review. When maximized the connection selector, log level configuration, and log table are removed from the view. You can restore the view at any given time using the same toolbar button.
      • You can now analyze external logs, whether loaded from files or pasted from the clipboard. External logs are opened in separate tabs in the Log Analyzer tool window.
    • The hierarchical view of a log can be used as an effective Apex Profiler. Resource metrics are automatically calculated based on the log contents at both the self (current scope) and roll-up levels. This is enabled by multiple view configurations (currently packaged with the product, but they will be end user-configurable in the future):
      • Standard Log - Displays the same information as the raw log, but organized hierarchically based on execution flow.
      • CPU Time and Memory Profiling - Displays a profiler-style view that includes CPU time and memory usage metrics. Log events are filtered to those relevant for time and memory profiling.
      • CPU Time Profiling - Displays a profiler-style view focused on CPU time metrics. As above, log events are filtered to those relevant for time profiling.
      • Memory Profiling - Displays a profiler-style view focused on memory usage metrics. Log events are filtered to those relevant for memory profiling.
      • Database Profiling - Displays a profiler-style view focused on SOQL query and DML metrics. Log events are filtered to those relevant for database profiling.
      • Cumulative Usage Limits and Profiling - Displays a bird's eye view that includes code unit cumulative limit usage organized by namespace and overall cumulative profiling metrics for hotspot identification.
      Each view configuration automatically expands the hierarchical view to a level that provides an appropriate starting point for analysis.
    • Two new profiling-oriented log level presets have added:
      • Sampling - Enables generation of information required for Apex profiling without enabling such detailed logging that proportional times are changes significantly. This is the most useful log level preset for profiling.
      • Tracing - Maximizes the information gathered in a debug log for analysis, but can change proportional times in a way that renders CPU time analysis invalid. This log level can be used to get a full view of everything that's happening during a process' execution but may not be as useful for metric-based analysis.
    • It is now possible to execute unit tests for profiling. A Profile run command is available for unit test methods and classes which automatically sets the log level to the user's choice of the two new profiling-oriented log level presets, then automatically opens the resulting log in the Log Analyzer hierarchical view as a separate tab with a profiling-oriented view configuration selected.
    • The tabbed raw/hierarchical log view is available in both the Log Analyzer and Anonymous Apex tool windows. It is not possible to add this view directly to unit test execution results, but a new unit test results toolbar button has been added, Show in Log Analyzer, which opens the current test execution log in Log Analyzer as a separate tab for more detailed review.
    • Log files up to the full 20MB are now supported.
  • Fixed several issues with the Apex Offline Debugger while implementing Log Analyzer, in particular relating to logs with multiple code units.
  • Fixed a few issues that could occur when deploying meta.xml files directly.

2.0.7.3 release notes

posted Jul 26, 2019, 6:58 AM by Scott Wells

2.0.7.3

  • Issues 1359 / 1362 - More updates to adjust for 2019.2:
    • Illuminated Cloud now works with a Java 11 host JRE.
      • NOTE: If you previously switched to a Java 8 host JRE using JB SDK Bintray Downloader, feel free to switch back. Either should work, though. The easiest way I've found to revert to the default Java 11 JRE is to remove the file idea.jdk / webstorm.jdk / etc. (the exact name is based on the host IDE) and restart the IDE. This file can be found under the config subdirectory of the base IDE's user-specific directory. You can also safely remove the jdks subdirectory found in the same location if no longer using the alternative JREs installed by the JB SDK Bintray Downloader, and you can uninstall the JB SDK Bintray Downloader plugin.
    • Fixed a few reference injections that were causing noisy messages in the log due to actual vs. expected reference injection host mismatches.
    • Note that string literal SOQL/RegExp injection is still disabled in this build. I am still working with JetBrains on a way to restore that feature that will work in as many base IDEs and versions as possible.
  • Issue 1358 - Prospective fix for an NPE during metadata deployment in certain situations.
  • Fixed an issue with the browser-based preview feature for Visualforce pages and Aura applications.
  • Fixed an issue that could occur during Apex test execution when the Coverage plugin isn't installed or enabled.

2.0.7.2 release notes

posted Jul 24, 2019, 5:11 PM by Scott Wells

Very shortly after I released 2.0.7.1 to address issues with WebStorm 2019.2, JetBrains released IntelliJ IDEA 2019.2 and PyCharm 2019.2. I updated the build for the new version which identified a few other issues with Illuminated Cloud 2 and the 2019.2 release family, most in IC2 but at least one in the base IDE for which I had to implement a quick workaround.

This release, 2.0.7.2, addresses all of the issues I've found with 2019.2 except for Java 11 support. A build of 2.0.7.2 with pre-release Java 11 support is available here. I hope to promote that to the official release in the next few days pending additional testing.

2.0.7.2

  • Issues 1359 / 1362 - The 2019.2 base IDE updates introduced some issues that are partially addressed in this build:
    • Had to disable SOQL/RegExp string literal language injection in all IDEs due to an incompatible plugin SDK change. JetBrains has provided guidance on how to register this feature conditionally based on the characteristics of the underlying IDE and plugin SDK. I'll implement this guidance in an upcoming build to restore the feature.
    • Improved the messaging around Java 11 JRE incompatibility, in particular what actions must be taken by the end user to move to a Java 8 JRE using the JB SDK Bintray Downloader. Full support for a Java 11 JRE is in testing now and will be available once I feel comfortable that it won't cause any issues.

2.0.7.1 release notes

posted Jul 24, 2019, 8:16 AM by Scott Wells

2.0.7.1

  • Issue 1359 - WebStorm 2019.2 introduced some issues that are (partially) addressed in this build:
    • Had to disable SOQL/RegExp string literal language injection in WebStorm as well. JetBrains has provided guidance on how to make this feature work properly in all IDEs. I'll implement their suggestion in an upcoming build to restore the feature in base IDEs where it's currently disabled.
    • Improved the messaging around Java 11 JRE incompatibility, in particular what actions must be taken by the end user to move to a Java 8 JRE using the JB SDK Bintray Downloader. Full support for a Java 11 JRE is in testing now and will be available once I feel comfortable that it won't cause any issues.

2.0.7.0 release notes

posted Jul 17, 2019, 9:39 AM by Scott Wells

2.0.7.0

  • Issue 821 - Added more explicit property types for classes in the Messaging namespace. OST regeneration is required to pick up this change.
  • Issue 1346 - Added another feature-based SObject suffix, __Tag. OST regeneration is required to pick up this change.
  • Issue 1347 - Fixed an issue introduced with 2.0.6.9 that could cause IntelliJ IDEA Ultimate Edition to fail to start if either the PHP or Ruby plugin was installed and enabled. This is due to JetBrains issue IDEA-218478. Unfortunately this means that SOQL/RegExp string literal language injection is not active in PhpStorm, PyCharm, or RubyMine until this issue is resolved.
  • Issue 1348 - Addressed some noisy errors and added a dedicated error reporter to help manage other error reporting noise.

1-10 of 103