Closed yahu1031 closed 2 years ago
This issue is aware of and already noted earlier. It is related to the changelog rendering issue. If that gets solved this gets solved too (same markdown rendering widget)
Duplicate of?
This feature will be removed until there is official API for Pub docs.
But this doesn't come under pub API.
And also, this is not a duplicate of #50. Cause the rendering is very different.
EG:
.exe
was showing in black or dark grey whereas, in docs, it was being converted to >
with a new line.
So this is neither a duplicate nor a pub docs API issue.
This issue will not be worked on as this docs feature for pub is removed until there is an official API for it.
Make it backlogged. Don't close it.
This feature NO LONGER EXISTS. It's gone forever until there is a docs feature in the future. Until then, this issue is closed. If there is a problem then please open it in a different issue. This issue please shall please remain closed.
That is why I backlogged and triaged it.
The feature won't come back anytime soon. And when it comes back, this issue will no longer be needed. I am aware of the docs rendering issue, it is not our issue, it is a dependency we are using that renders markdown. So facing the truth, it should be filed in their GitHub repo, not this repo.
As a sign of respect, please don't re-open this issue after this. Any bugs or errors reference them in new tickets, sincerely.
Remove the click functionality in the next commit and then I will review and close it.
It has already been removed. Push is pending.
Please review and close. Thanks 😊
Checked and verified.
Describe the bug Markdown on pub docs wasn't rendering correctly EG:
>
andcode blocks
.This back quote is being converted to
>
.Missing some tags (EG: Discord)
This tag gives
Error To Reproduce Steps to reproduce the behavior:
Expected behavior It must show the discord tag. Not only discord and some other packages tags were being missed.
Screenshots
Desktop (please complete the following information):
Logs (please upload the logs file by following the instructions): Unable to generate logs