aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | Remove blank line generated in config.ruclaudiob2015-12-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Follow the lines of the other `.tt` files ([example](https://github.com/rails/rails/blob/1611ab4db173a7596a7a94c58dabf1483f070304/railties/lib/rails/generators/rails/app/templates/config/environments/development.rb.tt#L26)) that have the space after the condition to avoid too many white lines in the resulted file.
* | | | | Explain what initializer/config_serializer doesclaudiob2015-12-181-0/+2
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | In line with the other initializers, add a short comment that explains what happens when you change the value of the initializer. [ci skip]
* | | / initializers/cookies_serializer is not new to 5.0claudiob2015-12-181-1/+0
| |_|/ |/| | | | | | | | | | | | | | | | | [ci skip] The initializer has existed since 4.1, for instance see: https://github.com/rails/rails/blob/v4.1.0/railties/lib/rails/generators/rails/app/templates/config/initializers/cookies_serializer.rb
* | | Change `alpha` to `beta1` to prep for release of Rails 5eileencodes2015-12-181-1/+1
| | | | | | | | | | | | :tada: :beers:
* | | Don't need to use `Array.wrap`Rafael Mendonça França2015-12-182-2/+2
| | |
* | | Merge pull request #22657 from matthewd/loosen-versionRafael Mendonça França2015-12-183-3/+17
|\ \ \ | | | | | | | | | | | | Allow normal version updates within a release series
| * | | Allow normal version updates within a release seriesMatthew Draper2015-12-183-3/+17
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We originally chose to apply very strict versioning on the `rails` entry in the Gemfile, because our future versioning policy was not strongly defined. Now it is, and our policy is very much designed on the expectation that people will regularly update to the latest patch level in their release series... so we should encourage that. Of course, Gemfile.lock will do its job and prevent unplanned updates, just as it does for every other gem in the bundle... but if you run `bundle update`, we want to get you the latest bug/security fixes without requiring a manual edit of the Gemfile entry. Our current version could be a few different shapes, so it takes a bit of work to find the right specifier, but in principle, we match anything of the form x.y.*, where x.y matches our current release series.
* | | Refer to rails command instead of rake in a bunch of placesDavid Heinemeier Hansson2015-12-181-1/+1
| | | | | | | | | | | | Still more to do. Please assist!
* | | Explain reason for eager loadingDavid Heinemeier Hansson2015-12-181-0/+1
| | |
* | | Explain Redis' role in Action CableDavid Heinemeier Hansson2015-12-181-0/+1
| | |
* | | Bring comment in line with rest of initializersDavid Heinemeier Hansson2015-12-181-2/+2
| | |
* | | Explain the concept of config initializers for backwards compatibilityDavid Heinemeier Hansson2015-12-183-2/+5
| | |
* | | Fix spacingDavid Heinemeier Hansson2015-12-181-1/+1
| | |
* | | These options are not changed nearly often enough to warrant inclusion like ↵David Heinemeier Hansson2015-12-181-8/+0
| | | | | | | | | | | | this at a high level
* | | Better explanationDavid Heinemeier Hansson2015-12-181-2/+6
| | |
* | | Use the rails command, not rake, for all rails commandsDavid Heinemeier Hansson2015-12-182-6/+6
| | |
* | | README.md in the app is now used to describe the app itself, not RailsDavid Heinemeier Hansson2015-12-181-1/+0
| | |
* | | More sensible ordering with the more important options firstDavid Heinemeier Hansson2015-12-181-12/+12
| | |
* | | List the major frameworks you can remove togetherDavid Heinemeier Hansson2015-12-181-3/+3
| | |
* | | fix indentation of generated controller testyuuji.yaginuma2015-12-182-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ``` # before module Bukkits class UsersControllerTest < ActionDispatch::IntegrationTest include Engine.routes.url_helpers setup do @user = bukkits_users(:one) end ``` ``` # after module Bukkits class UsersControllerTest < ActionDispatch::IntegrationTest include Engine.routes.url_helpers setup do @user = bukkits_users(:one) end ```
* | | Ignore Byebug command history fileAkira Matsuda2015-12-181-0/+3
| | | | | | | | | | | | | | | This file is generated by a gem that is bundled by default in the generated Rails app, just like .sqlite3 files. Hence it might be natural to be ignored here rather than in each developer's .gitignore_global.
* | | Use released rackRafael Mendonça França2015-12-181-2/+1
|/ /
* | Use release sprockets-railsRafael Mendonça França2015-12-171-1/+0
| |
* | Merge pull request #22627 from rails/application-mailer-by-defaultRafael França2015-12-176-14/+25
|\ \ | | | | | | ApplicationMailer should be generated by default just like every other Application* parent
| * | ApplicationMailer should be generated by default just like every other ↵David Heinemeier Hansson2015-12-176-14/+25
| | | | | | | | | | | | Application* parent
* | | Use released arelRafael Mendonça França2015-12-171-1/+0
|/ /
* | Generate API doc for actioncableArun Agrawal2015-12-171-0/+7
| |
* | Merge pull request #22068 from y-yagi/change_default_to_markdownRafael França2015-12-175-6/+6
|\ \ | | | | | | README.rdoc -> README.md for newly generated plugins
| * | README.rdoc -> README.md for newly generated pluginsyuuji.yaginuma2015-12-175-6/+6
| | | | | | | | | | | | I think Markdown is nowadays a better default.
* | | Merge pull request #22629 from ↵Rafael França2015-12-171-1/+0
|\ \ \ | | | | | | | | | | | | | | | | prathamesh-sonpatki/kill-extra-line-in-manifest-js Kill extra newline at the start of generated manifest.js
| * | | Kill extra newline at the start of generated manifest.jsPrathamesh Sonpatki2015-12-171-1/+0
| | | |
* | | | Puma 2.15.3 actually works fineDavid Heinemeier Hansson2015-12-171-1/+1
| |/ / |/| |
* | | Deal with leading CR when its not a mountable engineDavid Heinemeier Hansson2015-12-171-1/+1
| | |
* | | Include example of allowed_request_originsDavid Heinemeier Hansson2015-12-171-1/+2
|/ /
* | Don't mount the ActionCable server by defaultDavid Heinemeier Hansson2015-12-172-2/+2
| | | | | | | | | | | | Since we require you to enable it on the client-side, let us do the same on the server-side. Then you’re not running an EventMachine unless you need to.
* | No need to check for pumaRafael Mendonça França2015-12-161-1/+1
| | | | | | | | Rack::Server already does it work for us if the server is installed.
* | Avoid Action Cable stubs on --skip-action-cableDavid Heinemeier Hansson2015-12-163-3/+7
| | | | | | | | | | Still missing the stuff in app/ – we need to basically switch from a * match to specifically picking out what we need.
* | No longer needed now that we prefill with app/models/application_record.rbDavid Heinemeier Hansson2015-12-161-1/+0
| |
* | Generate all the ApplicationCable stubs by default, like all other ↵David Heinemeier Hansson2015-12-165-1/+20
| | | | | | | | Application* stubs
* | Saner incrementsDavid Heinemeier Hansson2015-12-161-3/+3
| |
* | Use puma as the default development server, if availableDavid Heinemeier Hansson2015-12-162-4/+4
| |
* | Eager loading is required for Action Cable and we should use the logging tooDavid Heinemeier Hansson2015-12-161-0/+4
| |
* | Only mount the ActionCable server if ApplicationCable has been definedDavid Heinemeier Hansson2015-12-161-1/+1
| |
* | By default, mount Action Cable on the routerDavid Heinemeier Hansson2015-12-161-0/+3
| |
* | Add default redis config for Action CableDavid Heinemeier Hansson2015-12-162-0/+9
| |
* | Merge branch 'master' into merge-action-cableRafael Mendonça França2015-12-169-33/+53
|\ \
| * | Use sprockets 3 in the Rails 5 releaseRafael Mendonça França2015-12-161-2/+0
| | |
| * | Merge pull request #22567 from gsamokovarov/introduce-application-recordRafael França2015-12-163-0/+15
| |\ \ | | | | | | | | Introduce ApplicationRecord, an Active Record layer supertype
| | * | Introduce ApplicationRecord, an Active Record layer supertypeGenadi Samokovarov2015-12-163-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's pretty common for folks to monkey patch `ActiveRecord::Base` to work around an issue or introduce extra functionality. Instead of shoving even more stuff in `ActiveRecord::Base`, `ApplicationRecord` can hold all those custom work the apps may need. Now, we don't wanna encourage all of the application models to inherit from `ActiveRecord::Base`, but we can encourage all the models that do, to inherit from `ApplicationRecord`. Newly generated applications have `app/models/application_record.rb` present by default. The model generators are smart enough to recognize that newly generated models have to inherit from `ApplicationRecord`, but only if it's present.
| * | | Update test generators to use ActionDispatch::IntegrationTestAbdelkader Boudih2015-12-154-25/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Rails 5.1 `ActionController::TestCase` will be moved out of Rails into it's own gem. Please use `ActionDispatch::IntegrationTest` going forward. This changes the generators to use `ActionDispatch::IntegrationTest` and the required URL setup (rather than symbols) for each of the controller actions. Updated fix to #22076.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 20:29:44 +0000