2.2.9.6 release notes

 2.2.9.6

• Issue 2484 - .forceignore filtering is now applied when collecting bundle files for deployment directly via the Metadata API. Note that there may still be a gap with regard to this issue if it's in the context of a metadata format project where .forceignore filtering is not currently applied at all.
• Issue 2486 - Addressed several missing lightning-card component attributes.
• Flow graphical preview improvements and fixes, round two
  • Replaced the Show/Hide Details toggle toolbar button with a more extensive Flow Diagram Settings toolbar button. Settings are configured at the IDE level by default but can also be configured at the project level if desired. When configured at the project level, settings are stored in .idea/illuminatedCloud.xml and can be safely stored and shared through version control. The following settings can now be configured to control Flow diagrams rendering:
    • Node details - Fine-grained options for which aspects of each node type should be included in the rendered output. All node types include a header section, and most node types also include one or more one-to-many collections of other details, e.g., inputs, outputs, conditions, etc.
    • Curve style - The style in which connector curves are rendered. My personal favorite is monotoneY.
    • Use experimental 'elk' renderer - When checked, the elk renderer is used:
      
      The layout of the diagram is done with the renderer. The default renderer is dagre. Starting with Mermaid version 9.4, you can use an alternate renderer named elk. The elk renderer is better for larger and/or more complex diagrams. The elk renderer is an experimental feature.
      
      Note that the elk renderer does not use the specified curve style, so that option is disabled when the elk renderer is enabled.
    Other options that might be added in the future (no guarantees on whether/when, though):
    • Whether to use a light theme, dark theme, or the IDE's configured theme.
    • Node type-specific background colors for light and dark themes.
  • Added node type-specific icons.
  • Added support for navigation to the corresponding source XML element when a node is clicked. The full XML element is also selected so that it's visually distinct. Note that because of the nature of the embedded browser integration and therefore some non-deterministic browser initialization timing, there may be (hopefully very rare) instances where the link handler is not initialized properly. It should be tuned pretty well at this point, but if you see this behavior with any real frequency, please let me know and I'll try to tune it a bit further.