Fix markdown formatting in example table #858
Merged
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
JoeRobich
approved these changes
Nov 10, 2020
|
@am11 Thanks! |
|
Thanks! I am using nightly builds, but are there plans to publish v5.0 to nuget.org (and github releases)? |
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.
@jmarolf, sorry I've just noticed that the markdown in the README did not wrap the lines in rendered view as I was expecting. We can either wrap the code and get the bad/unexpected rendered view or have long lines in code to get the text wrapped nicely in the rendered view (limitation of GH markdown).
This changes the table layout in rendered view from
to