From eb4deb9dc6493de5b7d452a0500707dd8ce69200 Mon Sep 17 00:00:00 2001
From: Kasper Timm Hansen <kaspth@gmail.com>
Date: Sat, 5 Dec 2015 21:30:18 +0100
Subject: `exists?` isn't for users.
Checking that a command exists before running it is an implementation detail
of the Rails command and Rake task world right now.
Eventually I'd like to get rid of `exists?`, when I've worked out another way
to fall back to run the old tasks.
---
railties/lib/rails/commands/command.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
(limited to 'railties/lib/rails')
diff --git a/railties/lib/rails/commands/command.rb b/railties/lib/rails/commands/command.rb
index 2e99046e9a..0d4d44ff89 100644
--- a/railties/lib/rails/commands/command.rb
+++ b/railties/lib/rails/commands/command.rb
@@ -31,7 +31,7 @@ module Rails
options_for(command_name) { |opts, _| opts.banner = banner }
end
- def exists?(task_name)
+ def exists?(task_name) # :nodoc:
command_name = self.class.command_name_for(task_name)
!command_for(command_name).nil?
end
--
cgit v1.2.3