2.2.0.5 release notes

 2.2.0.5

  • Issue 2038 - Fixed an Apex parser issue that would occur when an incomplete statement is entered just before a local variable declaration that is of an Apex primitive type. This should provide improved parser error recovery and therefore better code completions, references, etc., in both the incomplete statement and the following variable declaration.
  • Issue 2041 - Fixed an issue with tabbed editors that would occur for files that already use a tabbed editor independent of IC2, e.g., *.csv files (and similar) in commercial JetBrains IDEs which include tabs for both raw text and grid-oriented views. Now the existing sub-tabs are used instead of IC2's Source sub-tab alongside other sub-tabs such as Metadata.
  • IMPORTANT: Eliminated the need for an overridden Save All action for reliable deploy-on-save behavior. If the Override Save All action option was previously enabled, the system Save All action will be restored in the current keymap. If the Deploy on save option was enabled, typing Ctrl/Cmd+S or using the menu/toolbar equivalents will continue to initiate a deploy-on-save if Salesforce metadata files are selected. If the Deploy on save option was not enabled but the Override Save All action was, the user will be prompted once as to whether Deploy on save should be enabled.

    NOTE: The only users who should see a change in behavior as a result of this update are those who previously had Deploy on save enabled but not Override Save All action. For those users, deploy-on-save will now occur every time an explicit, user-initiated save is requested vs. previously where a deploy-on-save would have occurred only if the editor and file system contents differed.

  • Removed the Deploy all modified files and Deploy on external change options. Neither option ever did quite what users expected and would often lead to confusion when enabled.
  • Added a number of Tooling SObjects that are documented by Salesforce but are not present in OSTs generated against any of my test orgs. If these Tooling SObjects are reported by the API for an org, the org's version will be used instead of IC2's for highest level of accuracy and fidelity. These SObjects are included when the OST is next generated.
  • Changed the way that release notes are presented so that they're displayed in a dedicated editor tab instead of as a transient notification.