javadoc code tag language is not converted to markdown#1129
Merged
Conversation
Contributor
Author
…ed as the info string Co-authored-by: Tim te Beek <tim@moderne.io>
timtebeek
approved these changes
Jun 9, 2026
github-project-automation
Bot
moved this from In Progress
to Ready to Review
in OpenRewrite
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
2 participants
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.
What's changed?
Javadoc code tag is now converted correctly to Markdown.
What's your motivation?
Converting AssertJ project from Javadoc to Markdown.
Anything in particular you'd like reviewers to focus on?
Code style may be different - I can convert functional style to default if required.
Anyone you would like to review specifically?
@timtebeek
Have you considered any alternatives or workarounds?
Found none.
Any additional context
Checklist