fixing apidoc compliance post jdk23 part 1#8393
Merged
ebarboni merged 1 commit intoapache:masterfrom Apr 5, 2025
Merged
Conversation
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.
this is a first step to reduce to 300 linkage error. (was around 900)
Basically our previous link class.html#method-type- should be rewritten with class.html#method(type)
constructor link use # and need to be xml compatible using the following #%3Cinit%3E
same applied to array []
doc-files content is parsed by javadoc, so {@link } and others tag can be used. Make the javadoc a bit more semanticaly linked.
I started using @link when in text. I keep the old reference system when it's a code block. Could be nice to later have snippet instead the fuzzy html.
On infra side, h5 need to be checked for anchor reference