Added headerLevel capabilities... #11
Open
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
…added overloaded ToMarkdownHeader extension method to support headerLevel; added to the HeaderExamples test method.
|
This is my first time working with Git. After reading a little more it looks like I should have created a new branch - which I did not do. I hope that doesn't mess anything up. |
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.
...to HeaderBase, Header, and SubHeader; added overloaded ToMarkdownHeader extension method to support headerLevel; added to the HeaderExamples test method.
I modified the HeaderBase, Header, and SubHeader classes to produce markdown that translates to <h1> through <h6>.
Usage:
"This is wrapped an H3 element when translated to HTML.".ToMarkdownHeader(3);I only overloaded the
ToMarkdownHeader()method, not the subhead method, because I didn't see the point. Both methods would have produced the exact same results.Modifications are all done via method overloads and a little refactoring of private implementation code - so this constitutes a non-breaking change to the existing code base.