aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib
Commit message (Collapse)AuthorAgeFilesLines
* A generated app should not include Uglifier with `--skip-javascript` option.Ben Pickles2016-07-262-3/+9
|
* Enforce minimal web-console version for Rails 5Genadi Samokovarov2016-07-211-1/+1
| | | | | | | | | | | | | | | I dropped the version constraint in web-console with the idea it will be easier to upgrade the console between Rails releases. However, issues like #25899 started popping up. I'm reintroducing the constraint, but this time, I don't set an upper limit to the major version. This will keep the web-console in a version that always works for the current Rails version and can be easily upgraded to the last one with `bundle update`. We may need to backport this for Rails 5.0.1. Fixes #25899.
* Merge pull request #25438 from prathamesh-sonpatki/rm-session-store-initializerRafael Mendonça França2016-07-204-15/+25
|\ | | | | | | Setup default session store internally, no longer through an initializer
| * Setup default session store internally, no longer through an application ↵Prathamesh Sonpatki2016-07-174-6/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | initializer - By default the session store will be set to cookie store with application name as session key. - Older apps are not affected as they will have the session store initializer generated by Rails in older versions, and Rails will not overwrite the session store if it is already set or disabled. - But new apps will not have the initializer, instead the session store will be set to cookie store by default. - Based on comment by DHH here - https://github.com/rails/rails/issues/25181#issuecomment-222312764.
| * Refactor the existing session_store to use keyword args and raise early when ↵Prathamesh Sonpatki2016-07-171-9/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | set to activerecord session store - Use keyword args as it is possible to use them now. - The error message for activerecord-session_store gem was added in 1807384. - But it was added for a code path which gets called when we try to **access** the session store, not when we **set** it. - So the test expecting the exception started failing because now the session store is set via railtie again **after** setting it first with :active_record_store in the test. - As the error is not raised while setting the store to :active_record_store, the store gets overwritten by railtie and when we access it via `session_store` while building the default middleware stack, the exception is not raised. - This commit moves the code for raising the exception to the path where we try to set the store.
| * Introduce a new method for checking whether session_store is set by user or ↵Prathamesh Sonpatki2016-07-171-0/+4
| | | | | | | | | | | | | | | | | | | | | | by Rails - We need to ability to check whether the session store it is set or not so that we can set it ourselves in an internal initializer. - We can't rely on return value of `config.session_store` as it can return `nil` when set to `disabled` and we will accidentally override it and set to default cookie store. - So introduced new method which just tells us whether it is set or not.
* | Merge pull request #25795 from mechanicles/command-importanceGuillermo Iguaran2016-07-131-1/+1
|\ \ | | | | | | Give importance to rails command [ci skip]
| * | Give importance to rails command in the comment section.Santosh Wadghule2016-07-131-1/+1
| |/
* | Merge pull request #25690 from robin850/speed-up-rdocXavier Noria2016-07-121-0/+13
|\ \ | | | | | | Speed up RDoc generation when it's already been done once
| * | Speed up RDoc generation when it's already been done onceRobin Dupret2016-07-111-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Only include files that contain changes since the last generation of the API documentation. Thus, only modified files are re-generated instead of the whole API. The `created.rid` file won't contain the whole list of files anymore if we generate several times the API but we don't really care about it, only the generation date and time is important. It is possible to fall back to the previous behavior by defining the ALL environment variable running the `rake rdoc` task.
* | | rails -> Rails [ci skip]Santosh Wadghule2016-07-122-4/+4
| |/ |/|
* | Merge pull request #25688 from mahnunchik/host-env-varGuillermo Iguaran2016-07-081-0/+1
|\ \ | | | | | | Use the HOST environment variable for rails server #25677
| * | Use the HOST environment variable for rails server #25677Evgeny Vlasenko2016-07-051-0/+1
| |/
* | Merge pull request #25704 from ↵Rafael França2016-07-051-0/+4
|\ \ | | | | | | | | | | | | fledman/add_respond_to_missing_to_rails_application_configuration_custom implement respond_to_missing? to match method_missing
| * | implement respond_to_missing? to match method_missingDavid Feldman2016-07-051-0/+4
| | |
* | | Merge pull request #25692 from ↵Rafael França2016-07-051-0/+6
|\ \ \ | |/ / |/| | | | | | | | johnmeehan/allow-registering-directory-for-rake-notes Allow rake notes to work with other directories.
| * | Allow rake notes to work with other directories.John Meehan2016-07-051-0/+6
| |/ | | | | | | | | | | | | Additional directories can be added using SourceAnnotationExtractor::Annotation.register_directories("spec", "other_dir") Result: rake notes will now extract notes from these directories.
* | Merge pull request #25257 from ta1kt0me/inspect_initializersRichard Schneeman2016-07-052-1/+5
|\ \ | | | | | | Display railtie class name in `rails initializers`
| * | Initializer provides its context class nameta1kt0me2016-06-122-3/+5
| | |
| * | Delegate public method for raitile nameta1kt0me2016-06-112-1/+3
| | |
| * | Display railtie class name in `rails initializers`ta1kt0me2016-06-021-1/+1
| | |
* | | Point to the correct documentation [ci skip]Benjamin Quorning2016-07-051-1/+1
| | | | | | | | | | | | | | | | | | | | | The options used in this file are *not* directly described in the Rails 5.0 release notes (http://edgeguides.rubyonrails.org/5_0_release_notes.html), but instead in section 2 of the Guide for Upgrading Ruby on Rails document (http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html).
* | | Robots.txt removed disallow all instructionsSam Sweeney2016-07-051-4/+0
| |/ |/|
* | Merge pull request #25646 from y-yagi/refer_to_rails_command_instead_of_rakeVipul A M2016-07-021-3/+3
|\ \ | | | | | | refer to rails command instead of rake in doc of `SourceAnnotationExtractor`
| * | refer to rails command instead of rake in doc of `SourceAnnotationExtractor` ↵yuuji.yaginuma2016-07-021-3/+3
| | | | | | | | | | | | [ci skip]
* | | Merge pull request #25222 from vipulnsward/25219-fix-logsMatthew Draper2016-07-022-1/+13
|\ \ \ | |/ / |/| | Clean backtrace in IRB
| * | Fixes #25219Vipul A M2016-07-012-1/+13
| | | | | | | | | | | | Add handling of cleaning up backtrace from IRB console in case of errors
* | | fix task name to removeyuuji.yaginuma2016-07-021-1/+1
| | | | | | | | | | | | Follow up to #25431
* | | Do not run `bundle install` when generating a new plugin.Rafael Mendonça França2016-07-012-2/+2
|/ / | | | | | | | | | | Since bundler 1.12.0, the gemspec is validated so the `bundle install` command will fail just after the gem is created causing confusion to the users. This change was a bug fix to correctly validate gemspecs.
* | Merge pull request #25431 from ↵Rafael França2016-06-302-1/+10
|\ \ | | | | | | | | | | | | prathamesh-sonpatki/add-note-about-upgrade-guide-at-the-end-of-update Display link to Rails upgrade guide at the end of `rails app:update` task.
| * | Display link to Rails upgrade guide at the end of `rails app:update` task.Prathamesh Sonpatki2016-06-302-1/+10
| | | | | | | | | | | | | | | - This will nudge people in the direction of going through upgrade guides.
* | | Merge pull request #25607 from sstephenson/turbolinks-5-finalRafael Mendonça França2016-06-301-1/+1
|\ \ \ | | | | | | | | | | | | Update to Turbolinks 5.0.0 final
| * | | Update to Turbolinks 5.0.0 finalSam Stephenson2016-06-301-1/+1
| |/ /
* / / Point to released coffee-railsRafael Mendonça França2016-06-301-1/+1
|/ /
* | Initialize the configuration with a valueRafael Mendonça França2016-06-224-10/+2
| | | | | | | | | | | | | | This will fix the failures fixed by 41488adbb89a09fa96188486f8414842ff28c848 and keep this new option that is semi-private outside of the generated configurations
* | Fix failing railties testseileencodes2016-06-223-0/+9
| | | | | | | | | | Railties tests didn't know about the new config option added in 80b416f so it needed to be added to the railties generators for configs.
* | Add option to enable dependency loading in productionRafael Mendonça França2016-06-221-1/+1
| | | | | | | | | | | | | | | | This will make easier to applications that rely on having const_missing hooks in production upgrade to Rails 5. This option is going to be remove in the future and the default behavior will be to disable the dependency loading.
* | Fix rails/info routes for apps with globbing routeNicholas Firth-McCoy2016-06-201-1/+4
| | | | | | | | | | | | | | | | The /rails/info routes were inaccessible in apps with a catch-all globbing route, as they were being appended after the globbing route and would never be matched. See also ccc3ddb7762bae0df7e2f8d643b19b6a4769d5be.
* | No need to have conditional based on api options in assetsPrathamesh Sonpatki2016-06-201-2/+0
| | | | | | | | | | | | - As assets are removed for API only apps anyways, so we don't need any conditional upfront. - assets are removed for API apps here - https://github.com/rails/rails/blob/94ef224aa61ace3fa643eab161ff9056b7d90a62/railties/lib/rails/generators/rails/app/app_generator.rb#L266-L273.
* | Move quiet option to development.rbRafael Mendonça França2016-06-162-3/+3
| | | | | | | | | | This option is used in a initializer hook that runs before the config/initializers files so it will not work if it is set there.
* | Merge pull request #25004 from ↵Eileen M. Uchitelle2016-06-123-0/+21
|\ \ | | | | | | | | | | | | y-yagi/generate_mailer_layout_files_if_it_does_not_already_exist generate mailer layout files if it does not already exist
| * | generate mailer layout files if it does not already existyuuji.yaginuma2016-05-153-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, if `ApplicationMailer` does not exist, it is generated when run the mailer generator, but layouts files does not generate. However, because it uses the layouts in `ApplicationMailer`, layouts are required. Follow up to #24161
* | | Add config.assets.quiet = true as default valueKevin McPhillips2016-06-101-0/+3
| | |
* | | Merge pull request #25317 from prathamesh-sonpatki/fix-api-controller-testsKasper Timm Hansen2016-06-071-5/+5
|\ \ \ | | | | | | | | Fix API controller tests by assigning them the encoding type
| * | | Fix API controller tests by assigning them the encoding typePrathamesh Sonpatki2016-06-071-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - Fixes #25183. - The `as: :json` feature was added in https://github.com/rails/rails/pull/21671 and recommended to use for JSON endpoints so let's use it by default for API controller tests.
* | | | Flag `to_time` + simplify version names.Kasper Timm Hansen2016-06-071-5/+6
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | Since Ruby 2.4 isn't out yet, the fact that it will make `to_time` preserve the time zone should be toggled with a update flag. Second, remove the flipping on what version had what defaults. It's called new framework defaults, so it's from the future looking. Thus keep the line that mentions past versions.
* | | Use the `update` flag to provide more friendlier messages to people upgrading.Prathamesh Sonpatki2016-06-071-12/+9
| | |
* | | Remove FORCE option as it was only needed for testsPrathamesh Sonpatki2016-06-071-1/+1
| | | | | | | | | | | | - Adjusted tests instead.
* | | Update the documentation of new_framework_defaults file with more details ↵Prathamesh Sonpatki2016-06-041-13/+16
| | | | | | | | | | | | | | | | | | about old apps and how you can upgrade to new defaults. [Kasper Timm Hansen, Prathamesh Sonpatki]
* | | Fix minor regression about old apps not getting per_form_csrf and ↵Prathamesh Sonpatki2016-06-043-8/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | request_forgery_protection configs - Earlier per_form_csrf_tokens and request_forgery_protection config files were generated for old apps upgraded to Rails 5. - But when we collapsed all initializers into one file, the entire file does not get created for old apps. - This commit fixes it and also changes values for all new defaults for old apps so that they will not break. - Also added a test for `rails app:update`.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-08 22:20:30 +0000