fix: syntax error in class diagrams with nested generics#7489
fix: syntax error in class diagrams with nested generics#7489Sigmabrogz wants to merge 1 commit intomermaid-js:developfrom
Conversation
Closes mermaid-js#7480 - Changed inline class alias to standard block definition to fix parser error - Added space between nested tildes to prevent strike-through misinterpretation - Added missing colon to method return type to comply with Langium parser
|
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
@mermaid-js/examples
mermaid
@mermaid-js/layout-elk
@mermaid-js/layout-tidy-tree
@mermaid-js/mermaid-zenuml
@mermaid-js/parser
@mermaid-js/tiny
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #7489 +/- ##
=======================================
Coverage 3.52% 3.52%
=======================================
Files 509 508 -1
Lines 49790 49779 -11
Branches 785 785
=======================================
Hits 1754 1754
+ Misses 48036 48025 -11
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
Summary
Fixes the syntax error when attempting to define a class with an inline nested generic type and inline type definitions in the classchart.html demo file.
Problem
Closes #7480
The parser threw a "Syntax error in text" message in the
classchart.htmldemo. Specifically:~~) were misinterpreted as markdown strike-through tokens.: T), violating the Langium parser requirements.Solution
class People List~List~Person~~to a standard block definition.~ ~) to prevent the strike-through tokenization error.+getItem() : T).Testing
Checklist