Add a test to demonstrate our current handling of Javadoc that starts with a MOE comment.#1413
Merged
Merged
Conversation
… with a MOE comment. (I haven't checked what the actual rendered Javadoc would look like for such Javadoc, including what happens to the summary fragment. It might well be a bad idea.) I hope to change the behavior in unknown commit. PiperOrigin-RevId: 945817704
copybara-service
Bot
force-pushed
the
test_945784757
branch
from
c2fc51b to
211ff6f
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.
Add a test to demonstrate our current handling of Javadoc that starts with a MOE comment.
(I haven't checked what the actual rendered Javadoc would look like for such Javadoc, including what happens to the summary fragment. It might well be a bad idea.)
I hope to change the behavior in unknown commit.