| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \
| | | |
| | | | |
Fix API controller tests by assigning them the encoding type
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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.
|
|\ \ \ \
| | | | |
| | | | | |
reference actual class to use middleware
|
| | |_|/
| |/| |
| | | |
| | | | |
Using strings for middleware class names is deprecated in 83b767cef90abfc4c2ee9f4b451b0215501fae9a.
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| | |
| | |
| | |
| | | |
- Adjusted tests instead.
|
| | |
| | |
| | |
| | |
| | |
| | | |
about old apps and how you can upgrade to new defaults.
[Kasper Timm Hansen, Prathamesh Sonpatki]
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Move real new default options to the top of the file.
- After that club together all the options which were added to keep
backward compatibility. So all of them will get only one header.
- Based on https://github.com/rails/rails/pull/25231#issuecomment-222945173.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
guides/source/action_cable_overview.md
|
| | |/
| |/|
| | |
| | | |
http://edgeguides.rubyonrails.org/api_documentation_guidelines.html#english
|
| |/
|/| |
|
|\ \
| | |
| | | |
Collapse all new default initializers into a single file
|
| | |
| | |
| | |
| | |
| | |
| | | |
- Adjusted tests also for this new behavior.
- Based on the discussion in
https://github.com/rails/rails/pull/25184#issuecomment-222454583.
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
- These initializers are new defaults for Rails 5 and newly generated
apps do not need to change them.
- Fixes #25181
|
| |
| |
| |
| | |
Follow up to e45f388.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When changing the generated integration tests to assert redirects with
an absolute path this redirection check in `assert_redirected_to` against
the absolute response location would now pass:
https://github.com/rails/rails/blob/af245aaf3a1c447752a1b5895adddc66e5f73c00/actionpack/lib/action_dispatch/testing/assertions/response.rb#L55
Thus we'd break early instead of hitting `assert_operator` and have
2 fewer assertions per `assert_redirected_to` as `assert_operator`
is composed of 2 assertions internally:
https://github.com/seattlerb/minitest/blob/4e146b1515b19a5c474e39c174b037510f6dbc6e/lib/minitest/assertions.rb#L254-L258
Deduct 2 assertions for 2 redirects taking the expected count down by 4
in total for the two failing tests.
|
|\ \
| | |
| | | |
Remove public/ files for API apps
|
| | |
| | |
| | |
| | | |
- Fixes #25180
|
| | | |
|
| | |
| | |
| | |
| | | |
second is now irrelevant with the dedicated API mode
|
|/ / |
|
|\ \
| | |
| | | |
Build action_cable.js with Blade
|
| | |
| | |
| | |
| | | |
Introduced in d6f2000a67cc63aa67414c75ce77de671824ec52 and was only used by Action Cable. Now handled by Action Cable’s assets:compile task.
|
| | |
| | |
| | | |
Adding '$' to emulate shell syntax
|
| | |
| | |
| | | |
[ci skip]
|
|\ \ \
| |/ /
|/| | |
Use RAILS_MAX_THREADS as pool size on all adapters
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When RAILS_MAX_THREADS is set, the postgresql adapter uses it as the
connection pool size, so that there are always enough connections
available to serve Action Cable requests.
The same logic applies when using any other adapter.
|
| | | |
|
| | |
| | |
| | |
| | | |
[ci skip]
|
|\ \ \
| | | |
| | | | |
Un-hide helper and assets options for controller generator
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These options were hidden via 9b36cf0fa4cbdcb2e2072ef1b8179a98b13efce3,
but these options have tests written for them, and I believe that they
are supposed to be public API.
Fixes #24168.
|
| | | |
| | | |
| | | |
| | | | |
environments
|
|\ \ \ \
| |_|/ /
|/| | | |
Cable: Generate .js or .coffee files while generating channel as per the javascript engine of the application
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
javascript engine of the application
- Now we will detect what javascript engine user is using and based on
that we will generate either `.js` or `.coffee` version of the channel
file.
- This also needs a change in coffee-rails to override the `js_template`
method. Related PR https://github.com/rails/coffee-rails/pull/72.
- Currently coffee-rails gem sets
`config.app_generators.javascript_engine` to `:coffee` and using this
information we override the `js_template` to set the extension as
`.coffee` in coffee-rails gem.
- Using this approach, we can keep the `channel.js` and `channel.coffee`
files in the Rails repository itself.
- Additionally the `js_template` method can act as public interface for
coffee-rails gem to hook into and change the extension to `.coffee`
without maintaining the actual asset files.
[Prathamesh Sonpatki, Matthew Draper]
|
|/ / /
| | |
| | |
| | |
| | | |
Sorry, I missed a few places in my last PR. This should be the last of
'em :grimacing:
|
| |/
|/|
| |
| | |
Conventionally envs are ordered development -> test -> production.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
It is related with https://github.com/rack/rack/commit/7b66d2cdb80a4d6b44fa8c61d92e25fbbda1f152
|
| |
| |
| |
| | |
[ci skip]
|
| | |
|
|\ \
| | |
| | | |
remove unnessary option setting from test runner
|
| | |
| | |
| | |
| | |
| | | |
In order to prevent `OptionParser::ParseError` when specify the rake options to
`routes` task.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If run the test over the `rake` command, because of the test patterns is passed
via `rake_run` method, do not need to be obtained from the argv.
This probably fixes #24372.
|
| | |
| | |
| | |
| | | |
`railtie` is already a string!
|
| | |
| | |
| | |
| | | |
- Followup of https://github.com/rails/rails/pull/24709.
|