- 06 7月, 2017 1 次提交
-
-
由 Koichi ITO 提交于
-
- 02 7月, 2017 1 次提交
-
-
由 Matthew Draper 提交于
This reverts commit 3420a145, reversing changes made to afb66a5a.
-
- 01 7月, 2017 1 次提交
-
-
由 Kir Shatrov 提交于
-
- 30 6月, 2017 1 次提交
-
-
由 Dinah Shi 提交于
-
- 30 5月, 2017 1 次提交
-
-
由 Sam 提交于
-
- 26 5月, 2017 1 次提交
-
-
由 Andy Atkinson 提交于
-
- 19 5月, 2017 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-
- 07 5月, 2017 1 次提交
-
-
由 Ryuta Kamizono 提交于
-
- 16 4月, 2017 1 次提交
-
-
由 Kasper Timm Hansen 提交于
Allows users to not have remote forms by default, since there's more JS harness, e.g. bundling rails-ujs, otherwise. Also don't skip creating defaults file anymore. Sprockets isn't the only new config.
-
- 12 4月, 2017 1 次提交
-
-
由 yuuji.yaginuma 提交于
-
- 27 3月, 2017 1 次提交
-
-
由 ota42y 提交于
-
- 23 3月, 2017 1 次提交
-
-
由 claudiob 提交于
The "-j" option was added 5 years ago (https://github.com/rails/rails/commit/d9c39c3a) when we wanted to support prototype-rails and jquery-rails. Prototype is not as popular and jQuery is not a requirement anymore. Still the "-j" option can be used to install *any* gem that ends in "-rails". This "might" open security issues and does not bring great benefits anymore. If you know which "-rails"-ending gem you want to install, you can manually add it to the Gemfile just like any other gem.
-
- 22 3月, 2017 1 次提交
-
-
由 yuuji.yaginuma 提交于
This is necessary only when updating to Rails 5.0, it is not necessary for updating to 5.1. Related #24243
-
- 19 3月, 2017 1 次提交
-
-
由 yuuji.yaginuma 提交于
It can not check correctly with `defined?` ```ruby irb(main):001:0> Rails.application.config.active_record => {:maintain_test_schema=>true, :belongs_to_required_by_default=>true} irb(main):002:0> defined?(Rails.application.config.active_record) => nil ``` Follow up to #28469
-
- 18 3月, 2017 1 次提交
-
-
由 Matthew Draper 提交于
Instead of forcing new applications to carry an initializer that just switches things to what their default "should" be, we can handle it internally. The initializer is then only used by upgraders: it shows what the new default would be (commented out), while their upgraded application continues to operate as it did before. Under this model, a multiply-upgraded application could accumulate several new_framework_defaults_*.rb files, for each release series it has traversed. A given release series only needs to generate the latest, though, because we don't support `rails app:upgrade` while skipping releases.
-
- 15 3月, 2017 1 次提交
-
-
由 yuuji.yaginuma 提交于
`rails:update` was changed to `app:update` in 6fb31638. Therefore, I think that it is better that the test name is also `app_update`.
-
- 24 2月, 2017 1 次提交
-
-
由 Kasper Timm Hansen 提交于
-
- 23 2月, 2017 2 次提交
-
-
由 David Heinemeier Hansson 提交于
-
由 Kasper Timm Hansen 提交于
-
- 22 2月, 2017 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-
- 21 2月, 2017 2 次提交
-
-
由 Roberto Miranda 提交于
ref this commit seems that has not been merged into 3.7 https://github.com/puma/puma/commit/42bec4600c51ab8a1c1ee5a0e1b738a4ffd82bf2
-
由 eileencodes 提交于
* Adds test case test * Adds driver adapter test * Adds tests for capybara seleium driver (testing the settings not actually opening the browser to test capybara w/ selenium because that would so so so slow) * Adds tests for rack test driver * Adds tests for generators
-
- 08 2月, 2017 1 次提交
-
-
由 yuuji.yaginuma 提交于
-
- 03 2月, 2017 1 次提交
-
-
由 yuuji.yaginuma 提交于
-
- 23 1月, 2017 1 次提交
-
-
由 yuuji.yaginuma 提交于
When specifying the `pretend` option, expect that no processing will be done, so do not execute `git init` as well.
-
- 13 1月, 2017 1 次提交
-
-
由 dixpac 提交于
* If `--skip-git` is not specified initalize git repo when creating new rails app
-
- 10 1月, 2017 2 次提交
-
-
由 yuuji.yaginuma 提交于
This reverts commit 8cb3cdff, reversing changes made to 3bc747bd. Reason: This test already exists in `SharedGeneratorTests`. Ref: https://github.com/rails/rails/blob/master/railties/test/generators/shared_generator_tests.rb#L109..L112 https://github.com/rails/rails/blob/master/railties/test/generators/app_generator_test.rb#L55..L56
-
由 dixpac 提交于
-
- 01 1月, 2017 1 次提交
-
-
由 Prathamesh Sonpatki 提交于
- No need to remove bin/yarn separately for API only apps because :skip_yarn is set to true for API only apps. - Added a test for :skip_yarn config.
-
- 23 12月, 2016 1 次提交
-
-
由 Akira Matsuda 提交于
-
- 09 12月, 2016 2 次提交
-
-
由 Yuji Yaginuma 提交于
Follow up to 0d20530e
-
由 David Heinemeier Hansson 提交于
-
- 02 12月, 2016 1 次提交
-
-
由 David Heinemeier Hansson 提交于
Move node_modules, package.json, and yarn.lock file to vendor
-
- 29 11月, 2016 3 次提交
-
-
由 Guillermo Iguaran 提交于
-
由 Liceth Ovalles 提交于
-
由 Liceth Ovalles 提交于
-
- 22 11月, 2016 1 次提交
-
-
由 Guillermo Iguaran 提交于
-
- 13 11月, 2016 1 次提交
-
-
由 Sean Griffin 提交于
-
- 02 11月, 2016 1 次提交
-
-
由 Bouke van der Bijl 提交于
-
- 25 10月, 2016 1 次提交
-
-
由 yuuji.yaginuma 提交于
If `sprockets` is not loaded, `Rails.application.config.assets` is not defined.
-