aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/commands/commands_tasks.rb
Commit message (Collapse)AuthorAgeFilesLines
* Remove the old command files.Kasper Timm Hansen2016-09-251-136/+0
| | | | | Wash out your old! These adhoc scripts are replaced by the new commands.
* refactor `CommandsTasks`yuuji.yaginuma2016-08-171-79/+35
| | | | | Extract a common method of `Rails::CommandsTasks` and `Rails::Engine::CommandsTasks` to the module.
* applies new string literal convention in railties/libXavier Noria2016-08-061-13/+13
| | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
* Merge branch 'rails-rake-proxy'Kasper Timm Hansen2015-12-131-5/+21
|\
| * Implement Rake proxy for Rails' command line interface.Dharam Gollapudi2015-12-131-0/+14
|/ | | | | | | Allows any Rake task to be run through `bin/rails` such as `bin/rails db:migrate`, `bin/rails notes` etc. The Rake tasks are appended to Rails' help output, and blend in as standard commands.
* Invert command and commands tasks reference.Kasper Timm Hansen2015-12-061-3/+1
| | | | | | | We should first attempt to run commands through Rails command, and then fall back to trying the commands tasks. Because eventually the commands tasks should be their own commands.
* Remove "run with rake" suggestion.Kasper Timm Hansen2015-12-061-22/+0
| | | | | | | | | When attempting to run a `rake` task with `bin/rails`, Rails would see check that a Rake task existed and ask users if they meant to run it with rake. We don't need that anymore, as the goal is to have `rails` be a valid way to run rake tasks.
* Add class level `run` to Rails command.Kasper Timm Hansen2015-12-061-4/+3
| | | | | | | | | | | | The class level version is responsible for changing a task name to command name, then finding a command and run it if there is one. The instance level `run` then makes sure arguments have been parsed into `@options` and runs the command by sending it. `Rails::Commands::Command.run` returns true to make it work within `Rails::CommandsTask`, but won't in the future when it handles all option parsing.
* Add Rails command infrastructure and encapsulate development cachingChuck Callebs2015-12-041-1/+5
|
* [ci skip] Document running a rake command as a rails commandNick Cox2015-04-151-0/+11
|
* spike of a `OptionParser` backed test runner.Yves Senn2015-03-181-1/+6
|
* use require_command! instead of calling its definitionAditya Kapoor2014-10-161-1/+1
|
* Let COMMAND_WHITELIST be an Array, not a StringAkira Matsuda2014-03-161-1/+1
|
* Removed unnecessary command "application"Arun Agrawal2014-03-101-6/+1
|
* More Warnings removed for ruby trunkArun Agrawal2013-11-011-1/+1
| | | | Same as 4d4ff531b8807ee88a3fc46875c7e76f613956fb
* Missing destroy commandAkira Matsuda & Yukiko Kawamoto2013-09-131-0/+4
|
* Using the instance variable for argv.wangjohn2013-07-091-2/+2
| | | | | Instead of using the global constant ARGV, we're changing to using the instance variable because it is more testable.
* Creating a class for carrying out rails commands.wangjohn2013-07-071-0/+170
This class encapsulates a lot of logic that wasn't very object oriented. Helper methods have been created to try to make things more logical and easy to read.