Yeah, you could do that, but you’d have to :nodoc: all the stuff you
It’d be cool to have an RDoc hooked tool that you could say something
resdoc accounts sessions pages
…and then it would crawl into your controllers directory, grab the
documentation for it, and then spit out a nice looking REST API doc
(which would likely look different than an RDoc). In RDoc, all the
methods would look like
update, etc for every controller,
making them indistinguishable. If a person wanted to learn about the
resources, they’d have to dig into your classes, and if they do that,
they’re looking at the docs for your app not the exposed API.
On Dec 20, 2007 6:19 AM, Ryan B. [email protected] wrote:
And actually that would be a cool tool.
skeleton documentation seems feasible. I could then fill the
changes are in
First of all let me congratulate all the team involved on the
Thank you for your support!
Ruby in Practice
My free Ruby e-book