I can reproduce this with sdoc master.
I've found part of the cause:
RDoc must not be generating things properly in this case. I've also narrowed it down to RDoc > 4.0.1 and < 4.1.0, so it was a change introduced in RDoc 4.1
Awesome @zzak, frenetic days over here my TODO is pilling up and appreciate the help ❤️.
I found the offending commit and reverted in RDoc master. (rdoc/rdoc@d96a7a7)
I'd like to get Eric's feedback, fix the offending regression, and release RDoc 4.1.2.
Since Rails generates the api reference documentation using the SDoc gem, and SDoc depends on rdoc ~> 4.0: a release of rdoc 4.1.2 will fix this. We will just need to regenerate the api reference docs after release.
rdoc ~> 4.0
@zzak just curious, any idea on when rdoc 4.1.2 will be out?
This issue has been automatically marked as stale because it has not been commented on for at least
The resources of the Rails team are limited, and so we are asking for your help.
If you can still reproduce this error on the 4-1-stable, 4-0-stable branches or on master,
please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.
Yeah, this is a bug in RDoc, will close this for now.