docs: fix backtick escaping in a Markdown file #58383
Closed
+4
−4
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
|
Deployed adev-preview for d537e14 to: https://ng-dev-previews-fw--pr-angular-angular-58383-adev-prev-eya7iiq5.web.app Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt. |
Member
|
@looshch Looks like you deleted the head repository hence closing the PR. |
Contributor
Author
|
@JeanMeche oops late night mistakes, i thought i saw a mention that the both mine PRs were merged 🤦🏼♂️. Sorry for this, here’s re-opened PR with everything being the same |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
Fix backtick escaping for the template string example in the documentation on expression syntax.
Closes #58382
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
there is an incorrect backtick escaping in the section about unsupported literals the documentation on expression syntax (highlighted on the first screenshot and without highlighting on the second one)
Issue Number: #58382
What is the new behavior?
the syntax is highlighted correctly
highlighted with a cursor
without cursor highlighting
Does this PR introduce a breaking change?