FEATURE: script/status

[GoogleCodeExporter]

This patch add a simple script (script/list) which list all the models,
controllers and services.

Original issue reported on code.google.com by jerome.l...@gmail.com on 8 Apr 2007 at 5:15

Attachments:

• patch-akelos-add-script-list.patch

[GoogleCodeExporter]

Thanks for this one :D

Why don't we evolve it into something like rails "rake stats"?
http://railsruby.blogspot.com/2006/01/rake-stats.html

So we can do something like 

    ./script/stats -v

for verbose stats like the one you provide with "list" and leave

    ./script/stats

for an output like rails one.

Things that can be listed should include

   Helpers, Controllers, Models, Services and Unit tests

And include details for

- Number of lines
- Code test coverage if possible (using something like
http://blog.liip.ch/archive/2006/01/05/visual-code-coverage-with-simpletest.html
)
- Number of methods
- Number of classes

This is much more work, but would be much more pragmatic to have that 
information and
not only something you can find out by just looking at your files and dirs.

Another thing that would be interesting to add is the possibility of filtering 
the
output.

I have applications where there are 40+ models and 15+ controllers, so its 
completely
useless for me to show everything at once. I'd rather go and scan my folders as
usual. So we can add something like this.

    ./script/stats --models

To get detailed information about models.

Let me know your thoughts about this.

Original comment by bermifer...@gmail.com on 9 Apr 2007 at 4:11

• Changed title: FEATURE: script/status
• Added labels: Type-Enhancement, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

I totally agree with you on this.

I made this quick script cause I hate to 'ls' in app/controller or app/models 
each
time I want to know what controllers and models I have.

Maybe we could add a first version of script/stats with only the listing of
controllers, models and services. And then, we have time to improve as the 
priority
of this issue is low.

Original comment by jerome.l...@gmail.com on 9 Apr 2007 at 8:50