Skip to content

More on RDoc formatting #4027

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

Closed
wants to merge 2 commits into from
Closed

More on RDoc formatting #4027

wants to merge 2 commits into from

Conversation

BurdetteLamar
Copy link
Member

@stomar is commenting along these lines in current documentation PRs, so let's get things settled in our guidance.

@BurdetteLamar BurdetteLamar added the Documentation Improvements to documentation. label Jan 5, 2021
@BurdetteLamar BurdetteLamar requested review from stomar and jeremyevans and removed request for stomar January 5, 2021 17:56
Copy link
Contributor

@jeremyevans jeremyevans left a comment

Choose a reason for hiding this comment

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

Thanks, I think this is a good change.

A code block should be preceded and followed by a blank line.
This is unnecessary for the HTML output, but helps in the ri output.

Consider whether <tt>=> ...</tt> in successive lines should be aligned.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Consider whether <tt>=> ...</tt> in successive lines should be aligned.
Consider whether comments (e. g. <tt># => ...</tt>) in successive lines should be aligned.

Copy link
Member Author

Choose a reason for hiding this comment

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

Have changed to "Consider whether # => ... in successive codeblock lines should be aligned."

@BurdetteLamar
Copy link
Member Author

I have an approval from @jeremyevans, and so propose th squash and merge. Any further improvements can be in a new PR.

@stomar
Copy link
Contributor

stomar commented Jan 6, 2021

Just to clarify the earlier discussion, I did not / do not suggest to everywhere replace string, array, hash with linked class names for those well-known core classes.

And, unrelated, too intrusive link layout could be fixed by using a less intrusive styling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Improvements to documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants