Hide embedded Racc runtime from generated API docs - #1799
Open
OskarEichler wants to merge 1 commit into
Open
Conversation
Member
|
We shouldn't update generated docs this way. Can we exclude them in |
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
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.
Summary
Wrap the Racc runtime embedded in the generated RD parsers with
:stopdoc:/:startdoc:markers, and teach the generator to reproduce those markers.This keeps the generated
RDoc::RDAPI while excluding the bundled parser-runtime implementation from RDoc output.Fixes #1762.
Verification
No test files were changed. Parser runtime behavior is unchanged; only generated documentation visibility changes.