feat: replace btoa with toBase64Url for encoding in drawMermaidImage #9505
Conversation
This file contains hidden or 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
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replace
btoawithtoBase64Urlfor encoding in drawMermaidImage.Since Mermaid Ink uses the encoded string in a URL, all characters must be URL-safe. Node names may include characters that are not URL-safe, which can cause a 404 error in Mermaid Ink.
as-is-url , to-be-url
Replacing
+,/, and=with-,_, and an empty string is defined in the RFC for URL-safe Base64, and Mermaid Ink supports this format.I also replaced btoa in the test code. The table below shows the encrypted URL before and after the change.
as-is
to-be