rails--rails/railties/lib/rails/commands/destroy.rb

require 'rails/generators'

if [nil, "-h", "--help"].include?(ARGV.first)
  Rails::Generators.help 'destroy'
  exit
end

name = ARGV.shift
Rails::Generators.invoke name, ARGV, :behavior => :revoke, :destination_root => Rails.root
Refactor generators a little bit. Signed-off-by: Yehuda Katz <wycats@mobile-166-129-219-135.mycingular.net> 2009-11-06 20:40:18 -05:00			`require 'rails/generators'`
Using Object#in? and Object#either? in various places There're a lot of places in Rails source code which make a lot of sense to switching to Object#in? or Object#either? instead of using [].include?. 2011-04-10 12:52:42 -04:00
removes usage of Object#in? from the code base (the method remains defined by Active Support) Selecting which key extensions to include in active_support/rails made apparent the systematic usage of Object#in? in the code base. After some discussion in https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d we decided to remove it and use plain Ruby, which seems enough for this particular idiom. In this commit the refactor has been made case by case. Sometimes include? is the natural alternative, others a simple \|\| is the way you actually spell the condition in your head, others a case statement seems more appropriate. I have chosen the one I liked the most in each case. 2012-08-05 18:27:56 -04:00			`if [nil, "-h", "--help"].include?(ARGV.first)`
Add missing -h/--help flag to several rails command [#3909 status:resolved] Signed-off-by: José Valim <jose.valim@gmail.com> 2010-02-09 08:19:54 -05:00			`Rails::Generators.help 'destroy'`
Updated commands. 2009-07-02 05:08:07 -04:00			`exit`
			`end`

			`name = ARGV.shift`
No more hacks to ensure generators are executed inside Rails.root. 2010-01-07 15:24:50 -05:00			`Rails::Generators.invoke name, ARGV, :behavior => :revoke, :destination_root => Rails.root`