| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
[ci skip]
|
|
|
|
| |
[ci skip]
|
|
|
|
|
| |
This reverts commit 4973704bf56dbb0d8beba977e1053d57e346ebd0, reversing
changes made to 78edeb33346e13ab33a62d2a6b553aabf5b3186a.
|
|
|
|
|
| |
Now the schema dumper by default doesn't align the types and arguments
in the ruby format anymore.
|
| |
|
|
|
|
| |
- It is Action Controller config, not Action View.
|
|
|
|
| |
Follow up to fe859a54219740fa8b4e09a592820d2ee12ba222
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement naive partial caching mechanism.
Add test for LogSubscriber
Use ActionView::Base#log_payload to store log_subscriber's payload, so we can pass cache result into it.
Fixed tests
Remove useless settings
Check if #log_payload exists before calling it. Because other classes also includes CacheHelper but don't have is attribute
Use @log_payload_for_partial_reder instead of #log_payload to carry ActionView's payload.
Update test's hash syntax
Add configuration to enable/disable fragment caching logging
Remove unless test and add new test to ensure cache info won't effect next rendering's log
Move :enable_fragment_cache_logging config from ActionView to ActionPack
Apply new config to tests
Update actionview's changelog
Update configuration guide
Improve actionview's changelog
Refactor PartialRenderer#render and log tests
Mute subscriber's log instead of disabling instrumentation.
Fix typo, remove useless comment and use new hash syntax
Improve actionpack's log_subscriber test
Fix rebase mistake
Apply new config to all caching intstrument actions
|
|\ |
|
| |
| |
| |
| | |
That file has been removed and replaced with new_framework_defaults.rb
|
| | |
|
|\ \
| | |
| | |
| | | |
Setup default session store internally, no longer through an initializer
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
| |
- Followup of https://github.com/rails/rails/commit/451437c6f57e66cc7586ec966e530493927098c7
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Follow up to #24436
|
| |
| |
| |
| |
| |
| | |
guide [ci skip]
- Also to_time_preserves_timezone config should be false for older apps getting upgraded to Rails 5 [ci skip]
|
|/
|
|
| |
Follow up to 5f777e4b5ee2e3e8e6fd0e2a208ec2a4d25a960d
|
|
|
|
|
|
| |
[ci skip]
r? @rafaelfranca
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SSL_set_verify(3) explains:
SSL_VERIFY_FAIL_IF_NO_PEER_CERT
Server mode: if the client did not return a certificate, the TLS/SSL
handshake is immediately terminated with a "handshake failure" alert.
This flag must
be used together with SSL_VERIFY_PEER.
Client mode: ignored
SSL_VERIFY_CLIENT_ONCE
Server mode: only request a client certificate on the initial TLS/SSL
handshake. Do not ask for a client certificate again in case of a
renegotiation.
This flag must be used together with SSL_VERIFY_PEER.
Client mode: ignored
The SMTP connection here uses a OpenSSL socket in client mode,
suggesting invalid/ignored flags is rather misleading.
|
|\
| |
| | |
Added some useful configuration options into configuring.md [ci skip]
|
| |
| |
| |
| |
| | |
Added information about inserting middlewares with indexes. I think this information useful. We can use indexes also for `insert_after` but the behavior is not same and this is not the right place to give full information about all configuration options.
The configuration for I18n fallbacks is important for production environment. Especially using different fallbacks for different locales.
|
| |
| |
| |
| |
| |
| |
| | |
`ActiveRecord::QueryCache` middlewares were removed with `Executor` addition on d3c9d808e3e242155a44fd2a89ef272cfade8fe8
Removes traces and reference of these from all places.
[ci skip]
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
guides/source/configuring.md
|
| | |
| | |
| | |
| | | |
config.action_dispatch.x_sendfile_header in configuring guide
|
| | | |
|
| | |
| | |
| | |
| | | |
be quoted as how other config options are. They are already quoted at many places. This change, makes this usage consistent. Note that, this is quoting literal values true and false, not truthy values
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
option
[ci skip]
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
guides [ci skip]
Guides should be updated because ActionDispatch::LoadInterlock was replaced with
ActionDispatch::Executor at #23807.
|
| | |
| | |
| | | |
Some configuration options started with a capital letter indicating the beginning of a sentence, which didn't makes sense without the colons. Similarly, some were missing periods at the end of their descriptions. [ci skip]
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Document config.assets.gzip flag.
|
| | |
| | |
| | |
| | |
| | |
| | | |
https://github.com/rails/sprockets-rails/pull/342.
[ci skip]
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Conflicts:
guides/source/configuring.md
|
| | |
| | |
| | |
| | | |
guide [ci skip]
|
| | |
| | |
| | |
| | | |
[ci skip]
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
- Make bulleted lists, end properly
[ci skip]
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
MariaDB documentation [ci skip]
|
| |/ / |
|
|/ /
| |
| |
| | |
behavior [ci skip]
|
| | |
|