fix: properly escaping app names #3368
Merged
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
gastonfournier
added a commit
that referenced
this pull request
Mar 22, 2023
## About the changes Network overview was not escaping square brackets from app names and that caused mermaid graph to break. We've also identified problems with quotes and some characters not showing properly when using utf-8 (but still no solution for this). We're going to be testing the utf-8 issue in our sandbox instances.
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.
About the changes
Network overview was not escaping square brackets from app names and that caused mermaid graph to break. We've also identified problems with quotes and some characters not showing properly when using utf-8 (but still no solution for this). We're going to be testing the utf-8 issue in our sandbox instances.