2.2.9.7 release notes
2.2.9.7
- Issue 2400 - Implemented a workaround for those experiencing OST generation failures due to:
This type of failure has become more prevalent and consistent in the past few days due to an issue that Salesforce has confirmed to be a bug in certain orgs, specifically those that include theStatus code 500 returned trying to retrieve .../completions/?type=apex
industriesintegrationfwk
namespace. The workaround included here uses a bundled copy of that API response from a "kitchen sink" org, i.e., one where as many optional features are enabled as possible. The resulting OST includes all core standard Apex types and should generally work fine for Apex development, but it will not accurately reflect the target org's set of enabled features and their corresponding Apex APIs, though it should be a superset and not a subset. Once Salesforce provides a fix for this bug, it should just be a matter of generating a new OST to include only the standard Apex types appropriate to the target org. - It is now possible to save Flow diagrams as HTML in addition to PNG by choosing
.html
as the file extension in the export dialog instead of.png
. The resulting HTML file is basically a wrapper around the diagram's SVG that includes the corresponding CSS, image references, etc. The HTML file is opened in the host system's browser automatically. Note that the SVG cannot be extracted from the resulting HTML file while retaining image integrity. When the Mermaid plugin maintainers resolve the existing issues with SVG diagram export, I will add SVG as a first-class file type option when saving diagrams.