-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
More on RDoc formatting #4027
Conversation
There 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.
Thanks, I think this is a good change.
doc/method_documentation.rdoc
Outdated
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. |
There 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.
Consider whether <tt>=> ...</tt> in successive lines should be aligned. | |
Consider whether comments (e. g. <tt># => ...</tt>) in successive lines should be aligned. |
There 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.
Have changed to "Consider whether # => ... in successive codeblock lines should be aligned."
I have an approval from @jeremyevans, and so propose th squash and merge. Any further improvements can be in a new PR. |
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. |
@stomar is commenting along these lines in current documentation PRs, so let's get things settled in our guidance.