Skip to content

Conversation

@st0012
Copy link
Member

@st0012 st0012 commented Jan 19, 2026

When using RDoc's features, there are some mistakes that can easily be detected by RDoc itself, such as missing rdoc-ref targets.

Currently RDoc only prints warnings to stdout. But to better notify users, it should exit the process with a non-zero status code.

I plan to use this system to implement more checks in the future.

When using RDoc's features, there are some mistakes that can easily be
detected by RDoc itself, such as missing `rdoc-ref` targets.

Currently RDoc only prints warnings to stdout. But to better notify
users, it should exit the process with a non-zero status code.

I plan to use this system to implement more checks in the future.
@matzbot
Copy link
Collaborator

matzbot commented Jan 19, 2026

🚀 Preview deployment available at: https://899dfbea.rdoc-6cd.pages.dev (commit: 510dcbb)

# At the end of rdoc execution, if any warnings were added, they will be
# printed and the process will exit with status 1.

class RDoc::Checker
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we don't instantiate this, we don't need to use class. module is better.

(And I think that we can improve name of this... This doesn't check anything. This just keeps reported warnings.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants