Fix < and > breaking the Javadoc output #4299
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
Coverage Report 1Affected Products
Test Logs |
Size Report 1Affected ProductsNo changes between base commit (4f41bde) and merge commit (34c1e72).Test Logs |
rlazo
approved these changes
Nov 9, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Per b/257287954, this PR fixes
<and>symbols breaking the doc output from Dackka.This occurs because angle brackets are broken in Dackka (see b/257276445). A workaround is to wrap them in
<code>blocks. Although, looking through our existing source, it seems as though we oftentimes wrap types in code blocks anyhow- so this PR just wraps the entire type versus just wrapping the generic type (what's present in the angle brackets).