CLOSED: Was addressing symptom not root cause #401
Closed
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
![blink-so[bot]](https://avatars.githubusercontent.com/in/1271127?s=60&v=4){kind=small}
Replace inline markdown link with separate text and link to prevent rendering engines from concatenating 'a' with '[Premium]' into 'aPremium'. Fixes the display issue where 'External agents require aPremium Coder license' was shown instead of 'External agents require a Premium Coder license'. Co-authored-by: Matt Vollmer <[email protected]>
blink-so
bot
changed the title
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.
Closing this PR
This PR was addressing the symptom rather than the root cause. The real issue is in the registry-server's markdown rendering pipeline, not the content itself.
The markdown
a [Premium](link)should correctly render as "a Premium" but the website is showing "aPremium". This indicates a bug in the markdown processor.See registry-server issue #378 for the proper tracking of this rendering bug.