I'm sold by your reply. Will reply to that ticket with 'No' response then :)
On Feb 10, 12:55 am, Jason King <[email protected]> wrote: > Boilerplate code is what it is, if you start trying to pick through it > to help with common tasks, where does it end? Something like renaming > a resource happens far more often than renaming a rails app, and yet > there's no expectation that the framework will do anything to help > users do that. > > My 2¢ is that generating code is worthwhile, editing existing code is > not. After the code is generated, it's up to the user. > > On Feb 9, 2010, at 12:41 AM, Prem Sichanugrist wrote: > > > > > Hello guys, > > > I found out a request ticket > > here:https://rails.lighthouseapp.com/projects/8994/tickets/3889-applicatio... > > regarding renaming the application name in Rails 3. > > > It seems to me that it's harder to rename an application in Rails 3, > > since there're namespaces and classes hard-coded in several files. > > > So, do you think it would help to add `rails rename new_app_name` to > > the list of actions, so users don't have to struggle with having to > > rename those files by themselves? > > > Cheers, > > > Prem Sichanugrist -- 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.
