-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Scaladoc crash when extending non-Scala-3 classes (short-term fix for 3.3.x) #16759
Conversation
ClassLikeSupport
getParentsAsTreeSymbolTuplesClassLikeSupport
getParentsAsTreeSymbolTuples
ClassLikeSupport
getParentsAsTreeSymbolTuplesClassLikeSupport
getParentsAsTreeSymbolTuples
Fixes scala#15927 Check for whether the non-scala3 parent exists before checking the start and end of the span to confirm whether the span exists in getParentsAsTreeSymbolTuples.
ClassLikeSupport
getParentsAsTreeSymbolTuplesThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this seems fine to me, I do not have enough familiarity with the scaladoc codebase to approve this PR
I therefore request a review from @rochala instead
@Florian3k can you take a look? |
I'm currently seeing this issue w/ scala 3.4.1 and sbt 1.10.1 I found it was due to having this: trait ~>[F[_], G[_]] {
def apply[A])( fa: F[A]) : G[A]
} Turns out scaladoc didn't like the "~>" name, so I renamed it. |
@aaronp Thanks for the report — this is helpful. Would you mind opening a new ticket on it? |
Sure thing - thanks! |
I've just had a go trying to create a minimum reproducible example to no avail, so I think I'll leave it for now. Thanks Seth |
Added jpath check to
ClassLikeSupport
getParentsAsTreeSymbolTuples — check for whether the non-scala3 parent exists before checking the start and end of the span to confirm whether the span exists in getParentsAsTreeSymbolTuples.Fixes #15927