* origin/release/10.3.1: (85 commits)
Version update and adjusted error diagram
Fix for broker error diagram related #4178
Adding new flowchart tests related to issue #2139
Fix for interim issue with classes in state diagrams
use default export in `error` diagram
create `ParserDefinition` type
standardized `error` diagram'
#2139 Applying user defined classes properly when calculating shape width
style: format packages/mermaid/src/config.type.ts
build(types): use prettier conf on config.types.ts
Syntax Update CONTRIBUTING.md
docs: Correct detectType filename
chore: Minor cleanups
chore: remove comment
chore: Remove comments, cleanup
fix!(deps): fix zenuml style leakage. update @zenuml/core to ^3.0.6 to fix the style leakage.
Update selectSvgElement.ts
create `Group` type
Add specialChars in textNoTagsToken, alphaNumToken
Return Unicode Text to idStringToken definition
...
Currently, the `packages/mermaid/src/config.type.ts` types file
(auto-generated via `pnpm run --filter mermaid types:build-config`)
uses the default prettier config.
Instead, we should use the prettier config in the Mermaid repo, as it's
slightly different from the default prettier config.
* develop: (59 commits)
fix!(deps): fix zenuml style leakage. update @zenuml/core to ^3.0.6 to fix the style leakage.
Update selectSvgElement.ts
create `Group` type
Add specialChars in textNoTagsToken, alphaNumToken
Return Unicode Text to idStringToken definition
Add underscore to unit test on special Chars
Revert to old docs concerning quotations marks in string
Refactor unit tests and remove repetition
Correct idStringToken definition to include all individual special tokens
Add unit tests for node ids with special Chars
Create lychee.toml
create `selectSvgElement`
change `svgElem` to `SVG` in `configureSvgSize`
add `configureSvgSize` in infoRenderer
run docs:build
remove info sandbox test case
Remove replaceAll method in addLink
Modify HREF token regex to contain space
Add unit tests for stange node names
Remove escaped quotes with backslash feature
...
This will ensure that alphaNumToken does not lose any of
the previously used tokens in its definition. The same
tokens were added to textNoTagsToken explicitly, because it used to
have alphaNumToken in its definition before I removed it.
Previously, textNoTagsToken and alphaNumToken had many tokens in
common in their definition. To avoid grammar conflicts, the
alphaNumStatement grammar was created. However, I found this
unintuitive and was an extra step just to avoid repetition in
the definitions.
I opted to have repetition in the definitions of textNoTagsToken
and alphaNumToken and it be explicitly clear right away, rather than
have extra grammar statements like alphaNumStatement which don't look
like they do anything at first glance
