| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / /
| | |
| | |
| | | |
of `rake routes`
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix description in cookies_serializer.rb being corrupted by gsub when updating
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | | |
Remove load_paths file
|
| |/ |
|
|\ \
| | |
| | | |
convert cable.coffee to cable.js
|
| |/
| |
| |
| | |
In order to eliminate the dependecy of CoffeeScript.
|
|\ \
| | |
| | | |
Deprecate :controller and :action path parameters
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Allowing :controller and :action values to be specified via the path
in config/routes.rb has been an underlying cause of a number of issues
in Rails that have resulted in security releases. In light of this it's
better that controllers and actions are explicitly whitelisted rather
than trying to blacklist or sanitize 'bad' values.
|
| | |
| | |
| | |
| | |
| | |
| | | |
These should allow external code to run blocks of user code to do
"work", at a similar unit size to a web request, without needing to get
intimate with ActionDipatch.
|
| | | |
|
|/ / |
|
| |
| |
| |
| | |
Changed description with tests related to rails_command.
|
| | |
|
|/
|
|
|
| |
- Ambiguous first argument
- Mismatched indentation
|
|\
| |
| | |
remove rack cors initializer when updating
|
| |
| |
| |
| | |
Rack cors initializer is only necessary to API-only applications, for when the update is unnecessary.
|
|\ \
| |/
|/| |
Use app namespace for framework tasks
|
| |
| |
| |
| | |
(e.g. `rails:update` and `rails:template` tasks is renamed to `app:update` and `app:template`.)
|
|/
|
|
|
| |
Puma 3.0 and up introduced compatibility to read from `config/puma.rb` when booting from the command `$ rails server`https://github.com/puma/puma/pull/856.
|
|\
| |
| | |
Enable HSTS with IncludeSubdomains header by default for new apps
|
| |
| |
| |
| |
| | |
- We will remove the initializer for old apps which are migrated to
Rails 5 so that they are not affected by this breaking change.
|
|\ \
| |/
|/|
| |
| | |
y-yagi/correctly_check_ApplicationRecord_in_mountable_engine
correctly check `ApplicationRecord` is exist in moutable engine
|
| |
| |
| |
| | |
Follow up to 1813b29fc7632959800252f36e4b2e6ed4ac7266
|
| |
| |
| |
| | |
This also marks Action Cable routes as internal to Rails.
|
|\ \
| | |
| | | |
Show permitted flag in the output of AC::Parameters#inspect
|
| | |
| | |
| | |
| | | |
- Fixes #23822.
|
|\ \ \
| |/ /
|/| | |
AppGenerator: Replace 'rake' with 'rails_command'
|
| | |
| | |
| | |
| | |
| | | |
Follows the convention from Rails 5 of invoking tasks on the command-line
with `rails …` rather than `rake …`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since Rails 5.0 is switching the Rails command line from 'rake …'
to 'rails …', it makes sense to also replace the `rake` method in
the Rails templates API.
Based on feedback from @matthewd and @kaspth, I chose to replace
`rake` with `rails_command`, which is less confusing than
the alternatives `rails` or `command` or `rails_run` and is not
Thor-reserved word like `task`.
|
| |/
|/| |
|
|\ \
| | |
| | | |
Alternative to #23638 log to STDOUT via env var
|
| | |
| | |
| | |
| | |
| | |
| | | |
People who deploy to containers or other places where they might have some sort of a log wrapping service use stdout. With this change new rails apps can be configured to output to STDOUT via setting `RAILS_LOG_TO_STDOUT` to any value. This allows container images or services to set the value for all apps without having to modify configuration for each application. If an app wants to opt out, they can either delete from the env hash, or remove that configuration.
cc/ @rafaelfranca
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
wisetara/wisetara/deprecate-args-ActiveSupport__TestCase#assert_nothing_raised-for-pr
Wisetara/deprecate args active support test case#assert nothing raised for pr
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
creating all databases mutates the connection pool. This patch restores
the connection pool to the connection spec established before creating
all databases. Fixes #23279
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
We should be able to pass options to minitest via TESTOPTS environment
variable
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Having collection caching that wraps templates and automatically tries
to infer if they are cachable proved to be too much of a hassle.
We'd rather have it be something you explicitly turn on.
This removes much of the code and docs to explain the previous automatic
behavior.
This change also removes scoped cache keys and passing cache_options.
|
|\ \
| | |
| | | |
move digest cache on to the DetailsKey object
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This moves digest calculation cache on to the details key object.
Before, the digest cache was a class level ivar, and one of the keys was
the hash value of the details key object:
https://github.com/rails/rails/blob/13c4cc3b5aea02716b7459c0da641438077f5236/actionview/lib/action_view/digestor.rb#L28
An object's hash value is not unique, so it's possible for this cache
key to produce colliding keys with no resolution. This commit move
cache on to the details key object itself, so we know that the digests
are always unique per details key object.
|
|/ /
| |
| |
| |
| |
| | |
If you want to use `EventedFileUpdateChecker`, need to specify `listen` to plugin's gemspec.
However, the default is not specified `listen` to plugin's gemspec,
`EventedFileUpdateChecker` should be disabled.
|
|\ \
| |/
|/| |
modify to `error` also abort when specify fail fast option
|
| | |
|
|/
|
|
| |
Now that AC::Parameters is no longer a Hash, it shouldn't look like a hash.
|
| |
|
|\
| |
| | |
Correct config option from only_api to api_only in test
|