Weekly GitHub Report for Mermaid

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is @mermaid-js/[email protected]

1.2 Version Information:

On March 25, 2025, a minor update was released that introduced a new Radar Chart feature, enhancing the charting capabilities of the platform. This addition reflects ongoing efforts to expand visualization options.

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. [TYPE: BUG / ERROR] [STATUS: TRIAGE] ZenUML: Comment blocks overlap diagram participants and message lines: This issue describes a problem in ZenUML diagrams where multiline comment blocks overlay and obscure participant boxes and message lines, making the diagram unreadable. The user reports that comments do not push the diagram content down but instead render on top, causing visual collisions with actors like Browser and Auth0.

   • The comments include a request for assignment, followed by maintainers noting that the provided code snippet is incomplete and that the issue cannot be reproduced in the latest Mermaid version, suggesting the problem may have been fixed already; they also clarify that ZenUML is an external package and any fix should be applied there.
   • Number of comments this week: 3

2. [TYPE: ENHANCEMENT] [STATUS: TRIAGE] Is Treeview with minimal markup possible?: This issue discusses the possibility of simplifying the markup required to create a treeview diagram in Mermaid by inferring the diagram type from the language tag alone, rather than requiring an explicit type declaration. It explores the pros and cons of this approach, including ease of use and potential conflicts with other diagram types, and questions whether such an inference would be philosophically acceptable within the Mermaid project.

   • The comments highlight concerns about the feasibility of heuristically guessing the diagram type since similar characters appear in other diagram types, such as ER diagrams. Suggestions include using a trailing slash for specificity or modifying the code fence to include the diagram type, but these approaches would require a philosophical shift and might affect syntax highlighting and user expectations.
   • Number of comments this week: 2

3. [TYPE: ENHANCEMENT] [STATUS: TRIAGE] [TYPE: NEW DIAGRAM] Concept Map (Mindmap connection lines): This issue proposes adding a Concept Map feature to the existing mindmap functionality, allowing users to draw arbitrary connection lines between different mindmap nodes to better represent non-linear relationships. The suggestion includes example syntax and highlights the potential benefits for documentation and idea organization, while questioning whether this feature overlaps with generic flowcharts.

   • The comments discuss assumptions about existing features, express interest in progress, emphasize the usefulness for documentation, debate the distinction between mind maps and concept maps, and propose a new conceptmap diagram type with example syntax that combines mindmap structure and flowchart flexibility.
   • Number of comments this week: 1

4. [TYPE: ENHANCEMENT] [STATUS: TRIAGE] [TYPE: NEW DIAGRAM] Diagram proposal: N x M matrix: This issue proposes the development of a generic N x M matrix diagram as an evolution of the existing 2x2 matrix in Mermaid, allowing users to create matrices with any number of rows and columns for various use cases such as risk matrices, startup maturity stages, and Wardley Mapping. The proposal highlights the need for this feature due to repeated user demand but currently lacks implementation details or syntax specifications.

   • Two comments express interest in contributing to the development of this feature, with one user explicitly stating a desire to work on it and another inquiring if anyone else is planning to take it up.
   • Number of comments this week: 1

5. [TYPE: ENHANCEMENT] [STATUS: TRIAGE] sequence diagram change color of one line: This issue requests the addition of a feature to change the color of a single line or message in sequence diagrams, as currently only default colors and fonts are supported. The user provides examples and screenshots to illustrate the need for this functionality in either ZenUML or Mermaid sequence diagrams.

   • The comments discuss possible approaches such as changing the theme of selected messages, provide a helpful styling syntax for ZenUML to achieve this effect, and conclude with agreement that the issue can be closed after the solution is shared.
   • Number of comments this week: 1

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

As of our latest update, there are no stale issues for the project this week.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 6

Summarized Issues:

• Layout and Metadata Access: This topic covers requests to enable layout algorithms to access arbitrary metadata on nodes, similar to subgraph shape data, allowing custom properties to influence layout behavior. Such enhancements would improve the flexibility and customization of diagram layouts in Mermaid.
• issues/8004

• Clickable Edge Links: This topic involves proposals to add a dedicated click link syntax for flowchart edges, enabling clickable edge labels without embedding HTML anchor tags. This would simplify the creation of interactive diagrams by providing native support for edge links.
• issues/8006

• Rendering and Theming Enhancements: This topic discusses improvements to Mermaid's rendering pipeline to emit theme colors as CSS variables with fallback values and add web compatibility features for normalized SVG output. These changes aim to support responsive embedding and host-theme adaptability without external post-processing.
• issues/8007

• Diagram Type Inference and Syntax Simplification: This topic covers the possibility of simplifying Mermaid markup by inferring diagram types from code fence language tags, reducing the need for explicit diagram type declarations. This would streamline the user experience when creating treeview diagrams.
• issues/8014

• Code Block Syntax Highlighting in Nodes: This topic proposes adding support for fenced code blocks with syntax highlighting inside flowchart nodes to improve visualization and display of source code within diagrams. This feature would enhance the clarity and usefulness of flowcharts containing code snippets.
• issues/8018

• Support for Industrial Single Line Diagrams: This topic requests adding support for Single Line Diagrams used in industrial settings, noting a Mermaid extension that partially addresses industrial standards but highlighting gaps in Mermaid's current capabilities. Enhancing support would better serve industrial diagramming needs.
• issues/8019

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 2

Summarized Issues:

• Diagram Rendering Issues: Several issues highlight problems with the rendering of diagrams, particularly with arrows and layout in complex flows. One issue notes that the Swimlane Diagram format appears visually awkward and requires manual line breaks for better readability, while another reports that arrows between subgraph elements in flowcharts break when a direction statement is used, causing connections to fail in newer versions.
• issues/7822, issues/7954

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 4

Key Open Pull Requests

1. fix(class): reuse declared classes in lollipop relationships: This pull request fixes the issue of duplicate synthetic interface nodes in class diagram lollipop relationships by reusing already declared classes or interfaces at the endpoints and only creating synthetic interfaces when the endpoints have not been declared, ensuring normalized name handling and adding regression tests for both directions of the relationships.

• URL: pull/8010

• Associated Commits: 6ceea, 993b0, b94f9, 144f1

2. feat: pass node shape configs to layout algo: This pull request enhances the layout algorithm by passing complete node shape configuration data as metadata to flowchart vertices, enabling consistent access to node metadata—including properties defined with @{} syntax—similar to how subgraph metadata is currently handled.

• URL: pull/8016

• Associated Commits: 08e60, e899c, 98a69, aada5

3. Emit theme colors as CSS vars with fallbacks; add webCompatibility SVG normalize: This pull request introduces two optional SVG post-processing configurations—cssVariableTheme, which emits theme colors as CSS variables with fallbacks to enable a single prerendered SVG to adapt to host light/dark themes, and webCompatibility, which normalizes SVG attributes for responsive embedding by managing viewBox, dimensions, preserveAspectRatio, and optionally removing hardcoded backgrounds—integrated into Mermaid’s SVG serialization pipeline with updated schema, types, documentation, and unit tests.

• URL: pull/8008

• Associated Commits: f599c, 4281b

Other Open Pull Requests

• Community Integrations and Spellcheck Updates: This pull request adds Sharayeh to the "Other" section of the community integrations list, highlighting its capability to convert Mermaid diagrams into high-resolution PowerPoint slides. Additionally, it updates the spellcheck configuration to include the term "Sharayeh," ensuring proper recognition of the new integration's name.
• pull/8017

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 8

Key Closed Pull Requests

1. ci(validate-workflow): update CI to fix PRs from forks: This pull request updates the continuous integration workflow for validating the lockfile by switching from pull_request_target to pull_request to fix errors when checking out code from forks, pins the actions/checkout version to avoid breaking changes, uses a blobless clone for efficiency, runs on a lightweight ubuntu-slim runner, replaces PR comment reporting with GitHub Actions step summaries while keeping failed checks visible, and simplifies shell scripts to improve security and maintainability.

• URL: pull/8003

• Associated Commits: 1d254, c51be, d651a, bda57, 90049

2. Revert fix(flowchart): respect per-subgraph direction keyword in Dagre layout- #7672: This pull request reverts a previous fix that implemented per-subgraph direction handling in the Dagre layout for flowcharts because it caused broken arrows between nested subgraphs, restoring the original edge-copying behavior, simplifying direction data management, and adding regression tests to ensure proper handling of nested subgraphs with outgoing links.

• URL: pull/8005

• Associated Commits: c0816, 90eee, a2e67, e9bb9

3. Fix leaf edges from directed subgraphs: This pull request fixes the layout handling of leaf edges in explicitly directed subgraphs by ensuring that simple leaf-edge cases remain in the parent graph to preserve alignment, while still extracting subgraphs with internal edges or nested clusters, thereby resolving issue #7954.

• URL: pull/7993

• Associated Commits: 6d455, a3515

Other Closed Pull Requests

• Sequence Diagram KaTeX Note Rendering Fixes: This pull request fixes an issue where KaTeX-rendered notes over a single actor in sequence diagrams were incorrectly remeasured as plain text, causing excessive padding. It removes the redundant re-measurement and ensures KaTeX note dimensions are accurately computed and preserved, while also adding unit and end-to-end tests to prevent regressions.
• pull/8015

• Argos E2E Test Scoping and Workflow Improvements: These pull requests address issues with Argos image uploads and E2E test scoping for forked pull requests. One reverts the default enabling of E2E test scoping due to build queue problems, while another introduces a new label-triggered GitHub Actions workflow for full Argos image uploads and improves input handling and label management.
• pull/7948, pull/7980

• Flowchart Alias Test Suite Restoration: This pull request adds the previously declared but missing aliasSet40 containing the collate and hourglass alias pair to the flowchart alias test suite. This restores visual regression coverage for that alias pair.
• pull/7972

• Structurizr C4 Element Rendering Migration: This pull request migrates the Structurizr C4 element rendering from a legacy bespoke SVG drawing method to Mermaid’s unified shape system. It introduces a c4ShapeAdapter that maps C4 elements to new unified shapes with updated styling, enabling an in-place transition without feature flags while preserving existing layout, relationships, and boundaries.
• pull/7842

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.

Access Last Week's Newsletter:

• Link