Display m.notice messages with proper markdown parsing - #115
Merged
Merged
Conversation
Owner
|
Thank you for the PR, I'm sorry that I've been absent from the project the last couple of months |
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.
This closes #114.
It adds the option to pass
NSColorvalues toFormattedBodyView, since that's the only way to display colored markdown (the notice messages should appear gray).FormattedBodyViewthen computes theNSAttributedStringright in the initializer, as opposed to during view rendering. This might even have some performance benefit, although I don't think it really makes a difference.