Enhance Support for GitHub Markdown Elements (*WIP) #98
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
…n for a better look more consistent with github markdown pages.
…inking test but may be environmental.
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.
🧐 What?
There are parts of the github markdown format that morty doesn't support, this starts to fill those gaps
🛠 How
👀 See
Github Alerts & Diff Markdown
Header now behave more like on Github
🙅♂️ Not Included
Dark-mode support -> this would require all components css to be updated to support this. So the alerts have just one setting (similar to the other current elements)
🐞 Related issue
Github Alerts don't render
Diff codeblocks don't render
The Blue linked coloured headers in the rendered files are both ugly and non-consistent with github rendering