Elk renderer not wokring on empty subgraph

[Alexandre-SCHOEPP]

Description

When using the elk renderer when a subgraph is empty, I get the following error : Cannot read properties of null (reading 're')

Steps to reproduce

1. Using Meramid 10.8.0 locally or live editor
2. select flowchart
3. initialize with default renderer set to "elk" as documented
4. create an empty subgraph
5. weep

Screenshots

Code Sample

Here is my minimum reproducible example:

## Works

:::mermaid
%%{init: {"flowchart": {"defaultRenderer": "dagre"}} }%%
flowchart TD
subgraph A
end
:::

## Does not work
:::mermaid
%%{init: {"flowchart": {"defaultRenderer": "elk"}} }%%
flowchart TD
subgraph B
end
:::

Here is my minimum reproducible example:

Works

:::mermaid
%%{init: {"flowchart": {"defaultRenderer": "dagre"}} }%%
flowchart TD
subgraph A
end
:::

## Does not work
:::mermaid
%%{init: {"flowchart": {"defaultRenderer": "elk"}} }%%
flowchart TD
subgraph B
end
:::

Setup

• Mermaid version: 10.8.0, latest in live editor
• Browser and Version: Tested on Edge, Chrome, and VSCode via the vscode-markdown-mermaid extension

Suggested Solutions

variable re seems to be at the root of the issue.

Additional Context

No response

[Yokozuna59]

Hi @Alexandre-SCHOEPP, thanks for reporting the issue.

But I wouldn’t really consider this an issue; subgraphs are just rectangles that wrap nodes according to their size; there is no point in creating empty rectangles with no nodes inside.

It’s kind of similar to the empty namespace in class diagram, see #4625 (comment).

Unless you’re suggesting to make the behavior similar to the default renderer, degre, to consider it a regular node:

flowchart
subgraph a
end

[Alexandre-SCHOEPP]

Hi @Yokozuna59 !

there is no point in creating empty rectangles with no nodes inside.

I regularly use this functionality in mermaid with the default renderer as it allows for flowchart that evolve with development. For example, if I suspect that there will be subsystems in the future, I often leave an empty subgraph.

I also tend to make rather complex graphs, which, I understand, is a bit beyond the typical usecase for mermaid, but having empty subgraphs allows me to :

• use the live editor to make the general structure before focusing on details (and, since order of items has an impact on the rendering, i do need it to work with the final renderer for readability)
• remove subcomponents quickly to make a copy of particularly complex graphs that focus only on one aspect.

Unless you’re suggesting to make the behavior similar to the default renderer, degre, to consider it a regular node:

I think that this needs to either be properly documented (as I didn't find my answer in your documentation) with an error message saying that this is an intentional choice, or, as you've said, be brought to consistency with both renderer.

Thank you for the work you do on mermaid, I love that it does not have to be a static graph, and I think that this would help move the project in that direction.