Add a mechanism to escape '+' fragments #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prior to this change, it was not possible to start a line with `+` at all, which is particularly problematic when you have a diff in literal blocks. Possibly a better long-term fix for this problem would be to disable all pre-processing between triple-backticks, but the ability to escape `+` at the beginning of a line seems useful in itself and is much easier to implement.
mrmanc
reviewed
Sep 2, 2022
| @@ -62,13 +62,22 @@ | |||
| | replace:'<backgroundimageopacity>','<!-- .slide: data-background-opacity="' | |||
| | replace:'</backgroundimageopacity>','" -->' | |||
| %}{% | |||
| assign first_char = line | strip | |||
There was a problem hiding this comment.
Was it important to remove the strip filter? I think this is there to make sure we still detect indented fragments. Looking at your change locally it looks like the indented fragment now renders with it’s parent rather than as a separate step.
|
I’ve found that this also impacts mermaid diagrams which have indented |
mrmanc
added a commit
that referenced
this pull request
Jan 6, 2025
This was causing issues with Mermaid state diagrams, as the `*` in the start and end nodes (`[*]`) was being interpreted as emphasis (`<em>` tags were finding their way into the DOM). I found inspiration in [this solution](https://revealjs.com/math/#markdown) in the reveal.js docs which uses a single backtick to wrap text in a `<code>` block, which prevents marked (the JS Markdown processor used by reveal.js) from processing the text as markdown. To accommodate this change I’ve tweaked our JS to strip the code tag out of the Mermaid diagram code. This change may also provide an alternative approach for #35. I’ve upgraded Mermaid to default to 11.0.2, and users can now override this version in their `config.yml` like this: `mermaid_version: 11.0.2`. 11.0.2 is the most recent which didn’t introduce weird rendering issues with state diagrams which I’ve not spent time investigating.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prior to this change, it was not possible to start a line with
+at all, which is particularly problematic when you have a diff in literal blocks.Possibly a better long-term fix for this problem would be to disable all pre-processing between triple-backticks, but the ability to escape
+at the beginning of a line seems useful in itself and is much easier to implement.