- DescriptionVersionDate GMTCommit / svn
- Ruby 22.214.171.124 p4892018-03-28630232018-03-28T14:50:57Z
- Ruby 126.96.36.199 p4592018-10-17651362018-10-17T15:34:45Z
- Ruby 188.8.131.52 p3642020-03-31678792020-03-31T11:42:18Z
- Ruby 184.108.40.206 p2292021-04-0567939* for contributors2021-04-05T11:46:35Z
- Ruby 220.127.116.11 p2052021-07-0767951* for contributors2021-07-07T10:38:58Z
- Ruby 18.104.22.168 p1912021-07-07a21a3b7d23* for contributors2021-07-07T10:48:22Z
- Ruby 3.03.0.2 p1072021-07-070db68f0233* for contributors2021-07-07T10:08:35Z
- Ruby mastermaster dev2021-10-16cc8ff8b50d* for contributors2021-10-16T10:39:13Z
- Rails 4.x gem22.214.171.124020-05-1511f2bdf75a2020-05-15T18:34:31Z
- Rails 5.x gem5.2.62021-05-0548661542a22021-05-05T16:59:15Z
- Rails stable126.96.36.19921-10-14711b241dfd2021-10-14T22:06:46Z
- Rails master7.0.0.alpha22021-10-15573bba3ba9* for contributors2021-10-15T22:25:43Z
Libraries below are created from the main branches
- Octokit master4.15.02021-08-0235d968fd2021-08-02T18:08:33Z
- Octokit 4-stable4.21.02021-09-09d729c0df2021-09-09T09:34:28Z
- SketchUp Ruby APISU2021.12021-09-0634faee42021-09-06T09:25:34Z
Please set font size, see settings...
Site updates done with
ruby 3.1.0dev (2021-10-16 master cc8ff8b50d) [x64-mingw32]
What does '* for contributors' mean?
Developers / contributors often remove objects from documentation which are not considered part of the public API.
Libraries listed as '* for contributors' show all objects, and are meant for contributors to the repository.
Hence, if you are using the API, you should not use any classes, modules, methods, or constants that are notated as 'for internal use only'. All of these items will have a red vertical bar (or border) distinguishing them from other objects. Please use the other library versions for API reference.
When you have a minute - UI Guide
YardT2 has quite a few features that are not based on RDoc or YARD. Please read the YardT2 UI Guide, in particular, the 'Search' information, as searching the 'Methods' list works for both name and namespace. 'Start of name' and 'anywhere in name' searches are supported.
All libraries are pulled from their respective GitHub repos. The branch / tag criteria is shown below. The last commit information and date (GMT) are retrieved via the GitHub API.
These libraries should correspond to the most recent ruby-lang.org packages. Only 'Ruby trunk' includes c source code.
- Ruby 2.2last tag matching v2_2_
- Ruby 2.3last tag matching v2_3
- Ruby 2.4last tag matching v2_4
- Ruby 2.5last tag matching v2_5
- Ruby 2.6last tag matching v2_6
- Ruby trunktrunk branch (current repo)
Version and date info is retrieved from version.h
- Rails 4.x gemlast tag matching v4.
- Rails 5.x gemlast tag matching v5.
- Rails stablelast 'stable' branch (currently 6-0-stable)
- Rails mastermaster branch (current repo)
Version info is retrieved from version.rb.
- YardT2 parses included do blocks.
- YardT2 parses alias_attribute, cattr, mattr, class_attribute, config_accessor, delegate, and deprecate statements.
- Most of the 'Rails Guides' appear in the 'Docs' list, and they link back to object documentation.
AWS SDK for Ruby
- AWS SDK for Ruby v3master branch
Version info is retrieved from VERSION file. At present, the gem is generated frequently, so the branch is rarely more than a few commits past the most recent gem.
As of April 2019, the AWS SDK for Ruby has almost 17,000 classes and modules, and 59,000 methods.
Loading the Methods list takes a long time, and is not a good idea on tablets. Once loaded, it searches well and is cached, unlike other implementations. Resizing the LIST pane when the Method list is visible is not recommended.
Simply put, loading 59k items into any DOM element is well outside of standard use.
Comments, Bugs, etc
For UI suggestions and other questions / comments...
A very special thank you to Loren Segal for his work in creating and maintaining YARD.
Also, thank you to all the contributors that have taken the time to comment / document these libraries.
- Release yard-t2 as a gem - need to write more tests, refactor some code, clean up css...
- Add code to detect super calls in method bodies?
- Add 'bundled gems' to Ruby documentation.
- Create code to document test code.
- Create code to document template code (erb, etc).
- Rails - more DSL methods to doc?
- RDoc - additional directives?