Fix escaped html characters in search result #1501
Merged
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.
What is the purpose of this pull request?
Resolves #1486.
Overview of changes:
Used
v-html
to render unescaped html characters (in place of the original mustache expression).Anything you'd like to highlight / discuss:
NIL
Testing instructions:
npm run test
Serve the user guide and search for "include" keyword.
<
and>
that originally appears should now be replaced by<
and>
respectively, since the characters are no longer escaped.Proposed commit message: (wrap lines at 72 characters)
Fix escaped html characters in search result.
Certain html characters are automatically escaped for
security reasons. However, it is not needed in our context
as the html is supplied by the user.
Let's prevent html characters from getting escaped so as
to render the html correctly.
Checklist: ☑️