Tweaking hover presentation #99
Closed
Conversation
This file contains 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
Collaborator
alanz
commented
May 8, 2020
alanz
commented
- Make sure the code fence markers start properly (hover improvements #97)
- Get rid of excessive line breaks
- Use a HR marker that works on emacs and vscode (Use friendlier value for sectionSeparator lsp#243)
- Put the detected types at the top, so they line up with the haddocks etc. This is the way hie does it, so you can easily see the polymorphic and monomorphic variants of the signature together.
jneira
approved these changes
May 8, 2020
|
It is included in #102 |
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.