-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/4381 markdown in sequence diagram #4725
base: develop
Are you sure you want to change the base?
Feature/4381 markdown in sequence diagram #4725
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #4725 +/- ##
===========================================
+ Coverage 77.05% 77.43% +0.38%
===========================================
Files 146 146
Lines 14573 14632 +59
Branches 592 594 +2
===========================================
+ Hits 11229 11331 +102
+ Misses 3225 3183 -42
+ Partials 119 118 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Note*: It seems that git diff goofed a bit for the |
8e70fc2
to
925a419
Compare
Seems like I'm having issues with conflicts in pnpm.lock. All I'm trying to do is merge develop into this branch. I have never downloaded an extra dependency or changed anything so I'm not really sure how this came about. |
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@ibrahimWassouf Hi! Any updates on this one? |
Hey! I got busy for a while and left this in this state obviously. In short, I can't think of a way to do this with the sequence diagram as it is (although I will have to check if the code changed significantly since starting). The issue is that strings are cut up into smaller, separate strings and stacked on top of each other. This means that if you had "A string with a a really long emphasis" is could be cut in two between the tags, preventing them from being properly rendered. The biggest issue I came across was that other elements in the diagram, such as the width of the actors/participant boxes or when the message arrow is rendered, are rendered dynamically based on the size of the message. Thus, creating a singe text label did not work at nicely as I'd hoped. It all seemed like spaghetti code to me, so I had trouble figuring it out. I started work on migrating the sequence diagram to typescript in hopes of understanding how the whole thing is rendered but didn't have the time to finish that up. I'll give it my best shot to give this another try, but feel free to unassign me from the ticket if you want to encourage others to give it a try as well! |
📑 Summary
Implements markdown in sequence diagrams
Resolves #4381 #1844 #
📏 Design Decisions
I've stuck to simply imitating what other diagrams have implemented and reused as much code as I could.
📋 Tasks
Make sure you
MERMAID_RELEASE_VERSION
is used for all new features.develop
branch