Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | [Railties] require_relative => require | Akira Matsuda | 2017-10-21 | 1 | -1/+1 |
| | | | | This basically reverts 618268b4b9382f4bcf004a945fe2d85c0bd03e32 | ||||
* | Adding frozen_string_literal pragma to Railties. | Pat Allan | 2017-08-14 | 1 | -0/+2 |
| | |||||
* | [Railties] require => require_relative | Akira Matsuda | 2017-07-01 | 1 | -1/+1 |
| | |||||
* | make all rails commands work in engine | yuuji.yaginuma | 2017-01-09 | 1 | -11/+6 |
| | | | | | | | | Currently, all rails commands can be executed in engine, but `server`, `console`, `dbconsole` and `runner` do not work. This make all rails commands work in engine. Related to #22588 | ||||
* | Run engine commands through command infrastructure. | Kasper Timm Hansen | 2016-09-25 | 1 | -4/+2 |
| | |||||
* | applies new string literal convention in railties/lib | Xavier Noria | 2016-08-06 | 1 | -2/+2 |
| | | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default. | ||||
* | make rake proxy work in rails engines | yuuji.yaginuma | 2016-01-31 | 1 | -32/+3 |
| | |||||
* | make test runner work correctly inside engine | yuuji.yaginuma | 2015-07-12 | 1 | -2/+4 |
| | |||||
* | rails -> Rails [ci skip] | Prathamesh Sonpatki | 2013-05-09 | 1 | -1/+1 |
| | |||||
* | removes usage of Object#in? from the code base (the method remains defined ↵ | Xavier Noria | 2012-08-06 | 1 | -3/+1 |
| | | | | | | | | | | | | | | | | | | | 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. | ||||
* | Give more detailed instructions in script/rails in engine | Piotr Sarnacki | 2012-05-04 | 1 | -0/+4 |
| | | | | closes #4894 | ||||
* | Add destroy alias to engines | Guillermo Iguaran | 2011-08-22 | 1 | -2/+3 |
| | |||||
* | Use namespace if it's a mountable engine | Stefan Sprenger | 2011-06-07 | 1 | -0/+1 |
| | |||||
* | Add destroy to engine's commands | Stefan Sprenger | 2011-05-27 | 1 | -2/+3 |
| | |||||
* | Move requiring engine out of the switch case | Stefan Sprenger | 2011-05-27 | 1 | -4/+3 |
| | |||||
* | Introducing engine commands | Stefan Sprenger | 2011-05-26 | 1 | -0/+37 |