Preserve angle brackets when converting @param <T> to Markdown#1141
Merged
Conversation
timtebeek
added a commit
that referenced
this pull request
Jun 24, 2026
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.
JavadocToMarkdownDocCommentwas dropping the angle brackets on generic type parameters, converting@param <T>into/// @param Tinstead of/// @param <T>. This happened because the Javadoc parser models a type-parameter name as aJ.TypeParameterwith the surrounding</>stripped, andprintJrendered only the inner name. The fix detects aJ.TypeParametername inconvertParameterand re-adds the angle brackets. AgenericTypeParametertest covering both a type parameter and a regular parameter is included and passes.