Announcements‎ > ‎

2.0.0.3/4/5 release notes

posted Dec 27, 2017, 7:38 AM by Scott Wells   [ updated Dec 29, 2017, 8:48 AM ]

2.0.0.3

  • Issue 765 - Fixed a long-standing issue with the Visualforce/Lightning markup code formatter at the boundary between HTML and {!...} expressions.
  • Issue 825 - Major performance optimizations for the unused declaration code inspection. Please let me know if you see new false positives/negatives or high CPU overhead while editing with this enabled for on-the-fly inspection.
  • Issue 827 - Fixed a code inspection false negative that occurs when an inner class of an @IsTest-annotated class extends another type and references its @TestVisible-annotated members.
  • Issue 832 - Fixed a code inspection false negative (and reference injection bug) when a local type name is also found in the OST from installed managed packages.
  • Issue 833 - Fixed an issue that could result in an NPE when navigating to related symbols.
  • Added a new code inspection, Unresolvable method or constructor signature, that verifies that the invoked method or constructor is correct. Currently the inspection only verifies agreement between the number of formal parameters and the number of invocation arguments. In the near future the illegal assignment inspection will be extended to ensure that types are also compatible.
  • Fixed an issue that prevented Ctrl+MouseWheel from zooming in Anonymous Apex and SOQL Query tool windows.

2.0.0.4

  • Issue 765 - Suppressed a very noisy error in the logs resulting from the change from 2.0.0.3.
  • Issue 835 - Prospective fix for a StackOverflowError while building the inheritance hierarchy.

2.0.0.5

  • Issue 836 - Addressed a performance regression—especially evident in live templates like iter—introduced with the fix for issue 832.
  • Fixed an issue where a primitive type used as an identifier name, e.g., Id, would be incorrectly injected with a reference to the primitive type as well.
    • NOTE: While IC isn't flagging projects as needing an OST update in this build, if you see false negatives—in particular around Id usages—regenerate your OST and close/reopen your project to see if it addresses the issue. If not, please let me know ASAP.
Comments