From: zverok.offline@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:96636] [Ruby master Bug#16472] OStruct documentation is lost
Date: Thu, 02 Jan 2020 22:05:08 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-83605.20200102220508.4a568476bbdad66f@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16472.20200102144133@ruby-lang.org
Issue #16472 has been updated by zverok (Victor Shepelev).
@marcandre, got it, thanks. https://github.com/ruby/ruby/pull/2810
----------------------------------------
Bug #16472: OStruct documentation is lost
https://bugs.ruby-lang.org/issues/16472#change-83605
* Author: zverok (Victor Shepelev)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v:
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
After this commit: https://github.com/ruby/ruby/commit/9be3295d53b6fd9f8a3ad8157aa0655b1976d8ac -- RDoc loses documentation attahed to OpenStruct class, see https://docs.ruby-lang.org/en/master/OpenStruct.html, which currently looks this way:
```
class OpenStruct
<here shoud be explanations>
Public Class Methods
```
`require` should be put above docs.
I'd provide PR myself, but I kinda lost between core repository and https://github.com/ruby/ostruct (which seems outdated)?..
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2020-01-02 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16472.20200102144133@ruby-lang.org>
2020-01-02 14:41 ` [ruby-core:96625] [Ruby master Bug#16472] OStruct documentation is lost zverok.offline
2020-01-02 19:06 ` [ruby-core:96635] " ruby-core
2020-01-02 22:05 ` zverok.offline [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-83605.20200102220508.4a568476bbdad66f@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).