Unescape HTML entities in the name and description of Fig completion specs#179
Merged
Conversation
kevinchevalier
approved these changes
Aug 13, 2025
kevinchevalier
left a comment
kevinchevalier
left a comment
There was a problem hiding this comment.
Whoa! Nice work fixing this so quickly.
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
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.
Many of the Fig JSON completion specs include HTML entities like
<. We don't process these escapes, which results in incorrect rendering.It's a fairly minor change to unescape HTML entities when converting Fig specs into our own completion types.
Before
After