Fix rendering of <placeholder> in DNS names#64932
Merged
Merged
Conversation
Contributor
|
@c-w : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Contributor
|
Looks good/verified. |
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
4 participants
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.
The rendering of
<ASE name>.appserviceenvironment.netand text using other placeholders that start with<and end with>characters is broken in the article "Create and use an Internal Load Balancer App Service Environment"..The problem is due to the
<ASE name>token getting interpreted by markdown as a custom HTML tag and therewith the text between the<and>characters doesn't show up (refer to screenshot below which highlights the problem areas in red underlines).To display the text correctly, the
<and>characters must be HTML-escaped (see for example how the "Use an App Service Environment" articles handles this). As such, this pull request fixes the rendering by replacing<with<and>with>.