Fix double-escaped HTML entities in package READMEs #123
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
Some package READMEs (e.g., node-red-opcua-x) were displaying HTML tags as literal text instead of rendering them. This was caused by HTML entities being stored in escaped form (<img> instead of <img>) in the database. The fix unescapes HTML entities before markdown processing to handle cases where HTML tags are stored as <img> instead of <img>. This ensures already-escaped content from storage renders properly while maintaining security through DOMPurify sanitization.
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.
Some package READMEs (e.g., node-red-opcua-x) were displaying HTML tags as literal text instead of rendering them. This was caused by HTML entities being stored in escaped form (<img> instead of![]()
) in the database.
The fix unescapes HTML entities before markdown processing to handle cases where HTML tags are stored as <img> instead of![]()
. This ensures already-escaped content from storage renders properly while maintaining security through DOMPurify sanitization.
See https://flows.nodered.org/node/node-red-opcua-x
Fixes #122