Fix duplicate member entries in Scaladoc generation #24712
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
Resolves an issue where Scaladoc was generating duplicate entries for the same members when combining results from multiple parser instances. The fix implements deduplication by creating a stable composite key from the member's location, full name, and kind. When duplicates are found, the entry with documentation is preferred, falling back to the first entry if none have docs. This ensures clean, non-redundant API documentation output. Co-authored-by: Bill Venners <[email protected]>
|
The one place where I saw this happening was AnyVal: 
This PR fixes that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Resolves an issue where Scaladoc was generating duplicate entries for the same members when combining results from multiple parser instances.
The fix implements deduplication by creating a stable composite key from the member's location, full name, and kind. When duplicates are found, the entry with documentation is preferred, falling back to the first entry if none have docs.
This ensures clean, non-redundant API documentation output.