2.2.0.1 release notes

 2.2.0.1

  • JetBrains 2021.3 update status - JetBrains has released 2021.3.1 updates for all supported IDEs. I have verified that the IDEs which omitted a required third-party class library in 2021.3 now restore that library, and IC2 works properly without its own bundled copy. As a result I have removed the bundling workaround starting with this version of IC2. NOTE: Please make sure that you have upgraded to 2021.3.1 (or higher if available).
  • Issue 2012 - Removed the distinct color/style settings for type parameters since there's really not a good way to make them behave as desired given that a type parameter can be a class, interface, or enum...and it already uses those settings properly.
  • Issue 2026 - Added percent-fixed as an allowed value for the LWC lightning-formatted-number component's format-style attribute.
  • Added a Refresh license status link to the expired and grace period license status notifications to provide a simple way for users in that state who have already renewed their subscriptions to inform IC2 of the new license status immediately.
  • Fixed issues with the Sfdc_Checkout namespace, specifically incorrectly-reported and missing system types. Note that the OST must be regenerated to see the effects of this change.
  • Fixed a reference resolution issue that could occur when an Apex class includes multiple non-method, non-constructor declarations with the same name but different declaration types, e.g., both an inner class and a field/property with the same name.
  • Changed the way that the unused declaration code inspection reports the declaration type so that it's more accurate and internally consistent.
  • Restored the use of sf env list to determine the current Salesforce Functions compute environment name now that it has been restored in the CLI itself. NOTE: Please make sure that you are on the latest version of the sf CLI, and if you continue to see an error when IC2 uses the CLI to query the compute environment name, please uninstall and reinstall the Salesforce CLI to ensure a clean installation. In my own testing (specifically on Mac) I encountered a situation where the CLI reported itself as fully up-to-date but was still using an older version of the sf env list command, and a full CLI uninstall/reinstall resolved the issue.
  • Other related fixes and improvements.