This project is archived and is in readonly mode.
![Brian Cardarella Brian Cardarella](https://entp-lh-avatar-production.s3.amazonaws.com/avatars/21518/large.jpeg?AWSAccessKeyId=AKIAJ4QBZRZBVMOUBNZA&Expires=2014695897&Signature=V63vm99PR4F1Bz9O0Dt0A0Hnv84%3D)
Let YARD document the railties gem
Reported by Brian Cardarella | September 3rd, 2010 @ 02:50 PM
It looks like railties was left out, not certain if that was intentional or not. But it would be nice to have the documentation for Generators accessible as well.
http://github.com/bcardarella/rails/commit/845520ee8821929be4fc11cf...
Comments and changes to this ticket
-
Brian Cardarella September 3rd, 2010 @ 03:25 PM
- Title changed from Let YARD document the railties gem to [PATCH] Let YARD document the railties gem
-
Jeff Kreeftmeijer October 10th, 2010 @ 08:53 AM
- Title changed from [PATCH] Let YARD document the railties gem to Let YARD document the railties gem
- Tag set to railties, yard
- Importance changed from to Low
Could you create a patch for this following the contributor guide and give this ticket the "patch" tag when you attach it instead of adding "[PATCH]" to the title? That'll make sure it ends up in the open patches bin. :)
-
Brian Cardarella October 10th, 2010 @ 01:06 PM
This ticket can be closed. I made a pull request on Github and Yehuda merged it on there.
-
Jeff Kreeftmeijer October 10th, 2010 @ 01:07 PM
- State changed from new to resolved
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>