Skip to content

Let group optionally display description info below nodes within the group#5389

Open
dceejay wants to merge 8 commits intodevfrom
Let-group-show-description-info
Open

Let group optionally display description info below nodes within the group#5389
dceejay wants to merge 8 commits intodevfrom
Let-group-show-description-info

Conversation

@dceejay
Copy link
Member

@dceejay dceejay commented Dec 16, 2025

…group

to help folk doc flows more visibly

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Proposed changes

Based of this discussion https://discourse.nodered.org/t/ways-to-improve-flow-documentation/99924
This PR adds an optional checkbox to the group config that when enabled shows the raw text from the description tab as visible text below the nodes in the group.

We can't easily render markdown as SVG so this just adds the raw text - but does respect line breaks so the user can create useful documentation.

Screenshot 2025-12-16 at 09 29 02

Checklist

  • I have read the contribution guidelines
  • For non-bugfix PRs, I have discussed this change on the forum/slack team.
  • I have run npm run test to verify the unit tests pass
  • I have added suitable unit tests to cover the new/changed functionality

@Steve-Mcl
Copy link
Contributor

Would be lovely if the text was rendered markdown?

Perhaps a foreignObject would work (and perhaps simpler than computing SVG elements from split text?)? 🤔

Something like

<svg xmlns="http://www.w3.org/2000/svg">
  <foreignObject width="100%" height="100%">

    <div xmlns="http://www.w3.org/1999/xhtml">

      <rendered markdown here>

    </div>
  </foreignObject>
</svg>

@dceejay
Copy link
Member Author

dceejay commented Dec 16, 2025

OK - I'll let you work out the maths for the size of the group boundary !

Though I do feel that as others have pointed out - if we went full markdown and diagrams in the editor it would take up too much space permanently... the compressed font and text that we have now doesn't seem too bad... so I'm not feeling the urge to try for extending to markdown rendering. Of course other PR's are available...

I think there are better options for much wordier docs - like click to expand or separate windows etc.

@dceejay dceejay added this to the 5.0 milestone Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants