Initial support for Markdown Javadoc.#1360
Closed
copybara-service[bot] wants to merge 0 commit intomasterfrom
Closed
Initial support for Markdown Javadoc.#1360copybara-service[bot] wants to merge 0 commit intomasterfrom
copybara-service[bot] wants to merge 0 commit intomasterfrom
Conversation
540cb0d to
1cacbb8
Compare
1cacbb8 to
53e2a76
Compare
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
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.
Initial support for Markdown Javadoc.
This is work in progress and may mangle some Markdown Javadoc comments. Later changes will address that.
Currently supported Markdown constructs: newline-separated paragraphs;
# Headings; and- Bullet lists.*Emphasis*and**Strong emphasis**should work too because they don't need any special treatment. Other constructs probably don't work, notably code blocks.The approach here is to identify where the Markdown constructs are and effectively insert that information into the existing logic for HTML constructs and Javadoc-specific constructs. The reason is that these constructs are still valid in Markdown Javadoc comments. So it makes sense to augment the existing logic rather than trying to make a complete parallel formatter.