On Dec 8, 12:11 pm, Ryan Bates <[EMAIL PROTECTED]> wrote: > On Dec 7, 7:36 pm, "Carlos Henrique Palhares" <[EMAIL PROTECTED]> > wrote: > > > Hi all! > > > I'll get straight to the point. Was good to see some scripts being > > moved to a plugin, but some others still not making much sense (for me > > :D) to be a script.... such as "generate", or "plugin"..... Wouldn't > > be better if they were rake tasks? > > > Such as "rake plugins:install", "rake plugins:uninstall", "rake > > generate:controller", "rake generate:model", "rake > > generate:plugin".... and others... ?
> Maybe it's because rake tasks don't handle arguments well? It would be > a pain to do this: > > rake plugins:install PATH='path/to/plugin' > rake generate:model NAME='User' ATTRIBUTES='name:string' > > Regards, > > Ryan I don't think rake is a good candidate for these. Ryan makes a good point about the argument syntax being a bit awkward, but rake is built for dependency-based tasks, not as a generic batch file runner. Script/generate doesn't really need a dependency framework around it: it's just a script that blurts out code. So I think it's better to keep them separate from rake. Jeff purpleworkshops.com softiesonrails.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
