1.8.2.6 release notes

posted by Scott Wells

1.8.2.6

  • Issue 965 - Fixed an issue with multi-line @param tags during internal ApexDoc generation.
  • Added a workaround for an issue with PMD 6.2.0 where it would fail due to an XML parse error. Note that this may cause issues with earlier versions of PMD, so all users are advised to upgrade to 6.2.0+ if problems occur.
  • Fixed a parser issue with ternary expressions in Visualforce/Lightning formulas.
  • Added missing process() methods to System.Approval.

2.0.1.7 release notes

posted by Scott Wells

2.0.1.7

  • Issue 958 - Prospective fix for an issue when commenting out a large block of code in WebStorm.
  • Issue 965 - Fixed an issue with multi-line @param tags during internal ApexDoc generation.
  • Added an Add Clarifying Parentheses code intention to help clarify binary expressions in composite expressions. Just type Alt+Enter (Windows/Linux)/Opt+Enter (Mac) while the caret is over any expression and you should be prompted for the intention. Note that there is one known issue with logical expressions not always being grouped together properly. I'll address that in a very near-term release.
  • Added a workaround for an issue with PMD 6.2.0 where it would fail due to an XML parse error. Note that this may cause issues with earlier versions of PMD, so all users are advised to upgrade to 6.2.0+ if problems occur.
  • Fixed a parser issue with ternary expressions in Visualforce/Lightning formulas.
  • Added missing process() methods to System.Approval.

1.8.2.4 release notes

posted Apr 9, 2018, 7:44 AM by Scott Wells

1.8.2.4
  • Issue 959 - Adjusted for an incompatible plugin SDK change in 2018.*.

2.0.1.6 release notes

posted Apr 6, 2018, 7:31 AM by Scott Wells

2.0.1.6

  • Fixed an issue with renaming of Apex classes with constructors.

2.0.1.5 release notes

posted Apr 2, 2018, 7:59 AM by Scott Wells

2.0.1.5

  • Issue 22 - Added occurrences support for Extract/Introduce Variable refactoring. This means that IC now finds other valid occurrences of the expression selected for extraction as a variable and offers to replace them with references to the extracted variable as well as the selected expression.
  • Issue 22 - Added an Extract/Introduce Constant refactoring. This refactoring also supports replacement of all valid occurrences within the same file. I also improved variable name suggestions for constants extracted from or initialized with string literal values based on the string literal text.
  • Added SOQL keyword cube as an allowed Apex identifier.
  • Issue 937 - More progress on the invalid PSI element issue that occurs over time. Again, this is not a full fix but continues to narrow the window of opportunity and makes it easier for me to perform root cause analysis.
  • Disabled inlining of variable array initializers which could result in invalid Apex.
  • Fixed an illegal assignment inspection false negative with expressions like Map<Id, Case[]> casesByContactId = new Map<Id, List<SObject>>();.
  • Other minor fixes and improvements.

2.0.1.4 release notes

posted Mar 26, 2018, 7:28 AM by Scott Wells

2.0.1.4

  • Issue 917 - Disabled reference injection for type names and improved reference injection for SOQL bind parameters in string literals. You can still include string literal type name references during rename operations by using Shift+F6 / Shift+F6 followed by Search in comments and strings and then carefully auditing the resulting references.
  • Issue 918 - Fixed an issue that could cause renames of Apex classes to fail when super. and this. explicit constructor invocations are used.
  • Issue 937 - It appears that I have another issue with elements becoming stale. This includes a partial fix and some additional diagnostic info to help corner it. I'll issue another build with the complete fix when I have it.
  • Issue 938 - Made the metadata container name (more) unique by including not just the connection name but also the username and hostname. If you've seen deployments fail while in a QUEUED state when working in a shared org, this should likely resolve the issue for you
  • Fixed an issue that could cause custom Apex classes to be omitted from the OST in orgs with large numbers of custom classes. If you've experienced this issue, please regenerate your OST after taking this build.
  • Other minor fixes and improvements.

1.8.2.3 release notes

posted Mar 26, 2018, 7:27 AM by Scott Wells

1.8.2.3

  • Issue 938 - Made the metadata container name (more) unique by including not just the connection name but also the username and hostname. If you've seen deployments fail while in a QUEUED state when working in a shared org, this should likely resolve the issue for you
  • Fixed an issue that could cause custom Apex classes to be omitted from the OST in orgs with large numbers of custom classes. If you've experienced this issue, please regenerate your OST after taking this build.

2.0.1.3 release notes

posted Mar 19, 2018, 7:17 AM by Scott Wells

2.0.1.3

  • Issue 912 - Fixed an NPE experienced by some users during OST generation.
  • Issue 919 - Yet more fixes for "Test ignored" issues, this one due to transitive compilation issues in triggers which are not reported as associated with any executed test class/method.
  • Issue 929 - Prospective fix for an IDE lock-up that could occur when running unit tests against an SFDX scratch org.
  • Improved handling for additional information written to standard error during SFDX CLI execution, in particular CLI update notifications.
  • Other minor fixes and improvements.

1.8.2.2 release notes

posted Mar 19, 2018, 7:16 AM by Scott Wells

1.8.2.2

  • Issue 912 - Fixed an NPE experienced by some users during OST generation.
  • Issue 919 - Yet more fixes for "Test ignored" issues, this one due to transitive compilation issues in triggers which are not reported as associated with any executed test class/method.
  • Issue 929 - Prospective fix for an IDE lock-up that could occur when running unit tests against an SFDX scratch org.
  • Improved handling for additional information written to standard error during SFDX CLI execution, in particular CLI update notifications.
  • Other minor fixes and improvements.

1.8.2.1 release notes

posted Mar 5, 2018, 7:52 AM by Scott Wells

1.8.2.1

  • Issue 894 - Significant performance optimizations for OST generation, in particular against orgs with large numbers of custom Apex classes (packaged or unpackaged). Note that the primary optimization does come with a few caveats listed below. Please let me know if you see any other negative effects of this change ASAP so that I can address them, and if you're seeing particularly notable performance gains (I've heard about 30-40 minute OST gen times going down to 2-3 minutes!), please share those details as well.
    • I've noticed that the new APIs can "lose" some global symbols from types in installed managed packages, in particular interface methods. I've reported this issue to Salesforce.
    • The final modifier is dropped from class constants in installed managed packages. This change should be benign, but I do want to make users aware of it. I've also reported this issue to Salesforce.
  • In addition to the OST performance optimizations, I also added a connection-level option, Ensure Field Read Access, to configure whether SObject fields should be made readable by the current user or not. IC does this by updating the current user's profile to have read access for all SObject fields. Without read access, fields are not included in the OST and are therefore not available for code completion, integrated documentation, navigation, etc., and will show up as unresolvable references in the editor. It is recommended that this option be enabled when working with any type of developer organization, e.g., DE orgs, Partner DE orgs, dev scratch orgs, etc. It would make sense to disable it against production, sandbox, and UAT orgs where authorization should be managed carefully.
  • Issue 865 - Prospective fix for an issue loading binary static resource bodies.
  • Issue 882 - Expanded the effect of @TestVisible annotations on enum types to provide access to class and instance methods such as name() as well as enum constants.
  • Issue 892 - Fixed an issue with ternary expression type inference.
  • Issue 895 - Fixed an issue that caused the type of List<List<ElementType>>[0] to be incorrectly inferred as List<ElementType>[].
  • Issue 902 - Fixed a long-standing issue with the way that inheritance relationships are determined. If you see any further false negatives around inheritance relationships, please let me know.
  • Issue 904 - Allowed future reserved words loop and of as valid identifier names in the Apex parser.
  • Fixed another few instances of "Test Ignored" issues. As before, the root cause issues should now be reported at the class level. If you see any further instances of "Test Ignored" without some type of directional guidance on how to resolve the issue, please let me know ASAP.
  • Fixed an issue that could result in the IDE locking up when applying USER_DEBUG-only filtering to unit test output.
  • Other minor fixes and enhancements.

1-10 of 27