Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you trying to accomplish?
Sen on the Why ciso8601? page:
Previously, one could include backticks in their node labels. However, Mermaid v10.1.0 introduced "Markdown formatting" (which despite its name is not Markdown, but just Markdown-style bold and italics) which uses the backticks as part of its delimiters. This broke these labels.
Also the "no" edges were being rendered as "n".
What approach did you choose and why?
I've changed the labels to no longer use the backticks. 🤷
I quoted the
no
edge labels, so they render correctly.What should reviewers focus on?
🤷. CI is failing due to unrelated issues (fixed in #158)
The impact of these changes
Node/edge labels will render correctly once again.
Testing
You can visit https://github.com/closeio/ciso8601/blob/movermeyer/diagram_fixup/why_ciso8601.md and see the rendered page with the fixes: