2.2.6.1 release notes

 2.2.6.1

• IcApexDoc integration improvements
  • Updated the IcApexDoc integration to support all new options added in 1.0.0.2:
    • IcApexDoc command-line options can now be read from an options file.
    • ApexDoc can now be generated for a namespace, either specified in the project's sfdx-project.json file or explicitly as a command-line argument.
    • Alternatively, if the sfdx-project.json file specifies a namespace that should not be used, IcApexDoc can be instructed to ignore it.
    • Org-only Apex types can be retrieved and included in the IcApexDoc run alongside local and standard Apex types so that inheritance relationships from local Apex types to org-only types are properly reflected in the generated ApexDoc.
    • Retrieved org-only Apex types can also be included in the generated ApexDoc if desired.
  • The parent directory of the sfdx executable used by IC2 is now explicitly added to the beginning of the PATH environment variable before executing apexdoc to ensure that the same Salesforce CLI is used. This is particularly useful on MacOS where an IDE process started from the Dock/Finder may not have the same environment as one started from the command-line.
• Public issue tracker update - Approximately one month after I was forced to take the IC2 public issue tracker offline, I have restored it to its original state. Hopefully there will be no further spam attacks on that scale, but if they do occur, I will again be forced to make it private until more complete safeguards have been added by Atlassian/Bitbucket. In the meantime, please feel free to log bugs, enhancement requests, etc., and comment on existing items. As always, your feedback on IC2 is invaluable and helps to shape my work on this product.