Issue #6381 has been updated by jamesbritt (James Britt).


"It would be helpful if ruby-doc.org started moving towards adding --all when building documentation."

Easily done (in fact, already done for a parallel set of docs)

The choice to omit --all as a default came from some discussions with members of the Ruby Documentation Project, and it was there that the idea of way to have an additional directive to manage doc visibility of came up.  Perhaps, though, the assumption was that too many implementation-centric methods would otherwise get abused.  

If :nodoc: is in place to control this then it's simpler to just use  --all by default on ruby-doc.org, so that's what I'll do, and problem solved.

Thank you!





----------------------------------------
Bug #6381: Useful methods like included don't appear in RDoc
https://bugs.ruby-lang.org/issues/6381#change-26776

Author: agrimm (Andrew Grimm)
Status: Third Party's Issue
Priority: Normal
Assignee: drbrain (Eric Hodel)
Category: 
Target version: 
ruby -v: ruby 1.9.1p378 (2010-01-10 revision 26273) [i386-mingw32]


=begin
Methods like (({Module.included})) and (({Module.private_constant})) don't appear in ruby-doc.org's documentation, because they are private methods. This can cause difficulty for new users of Ruby, for example in http://stackoverflow.com/q/10369876/38765

While there is a rationale behind not showing some private methods, because they are implementation details that should not be relied upon by users of Ruby, this isn't the case here.

This issue has been discussed in ruby-core:40662 and elsewhere, but is something that needs to be put in a bug tracker.
=end



-- 
http://bugs.ruby-lang.org/