Abandon formatting of a Markdown Javadoc comment if it contains unsupported constructs.#1398
Merged
Merged
Conversation
…ported constructs. This is much better than mangling the text of the comment. Of course, better still would be supporting the constructs, as hopefully we will eventually. PiperOrigin-RevId: 933718210
copybara-service
Bot
force-pushed
the
test_933327231
branch
from
0450391 to
ce80f77
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
1 participant
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.
Abandon formatting of a Markdown Javadoc comment if it contains unsupported constructs.
This is much better than mangling the text of the comment. Of course, better still would be supporting the constructs, as hopefully we will eventually.