| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/ / / / / / |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Use the same key as presented in doc
|
| | |/ / / / /
| |/| | | | |
| | | | | | |
| | | | | | | |
Ref: https://github.com/rails/rails/blob/a8217bb594a625fb46a6af1488c0bde4aeac4986/railties/lib/rails/generators/rails/app/templates/config/storage.yml#L24
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Fix non escaped character
|
| | |/ / / / /
| |/| | | | | |
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
intrip/30049-application-controller-renderer-defaults-automatic-reload-in-dev
Fix ApplicationController.renderer.defaults overriding in development
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously overriding ApplicationController.renderer.defaults wasn't
working effectively in development. In fact the override was unset every
time the code was reloaded. The solution is to wrap the code in a
`.to_prepare` block.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix dummy_app configuration
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Use `with_dummy_app?` in gitignore
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Deprecate support of older `config.ru`
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Since Rails 4.0, `config.ru` generated by default uses instances of
`Rails.application`. Therefore, I think that it is good to deprecate
the old behavior.
Related: #9669
|
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* Add migrations per rails engine conventions
* Fix failing tests
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Light grammar edits.
[ci skip]
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Active Storage: check for `app.secrets.secret_key_base`, not `app.config.secret_key_base`
|
| |/ / /
| | | |
| | | |
| | | | |
By default, apps only have the former set.
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Add Active Storage to Rails
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The test was passing before because it was not being testes correctly.
Now we create a different engine that is loaded before the already
exising and we make sure that the first call for isolate_namespace is
what takes effect.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
What we want to test is that two different calls to isolate_namespace
with the same module doesn't change the original railtie. We can do that
defining two different railties.
We can't call in the application because this method is not supposed to
be called in an Application class.
|
| | | |
| | | |
| | | |
| | | | |
And deal with a temporary test fix until we allow you to skip active storage.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Everything inside the app directory of a engine is autoload/eager loaded automatically so we don't need to require them.
|
| | | |
| | | |
| | | |
| | | | |
It's worth considering whether we should hide these by default, but I'm kinda thinking no. It's very reasonable that someone would want to call these directly, so they should be documented.
|
| | | |
| | | |
| | | |
| | | | |
cc @rafaelfranca
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \ |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
With Active Storage supporting Azure, we should show people how to set it up.
Incorporates the minor changes originally in https://github.com/rails/activestorage/pull/88 as well
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
y-yagi/use_assert_nil_if_value_is_nil_in_assert_field_default_value_
Use `assert_nil` if `value` is nil in `assert_field_default_value`
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | | |
It is deprecate to specify nil for expect argument of `assert_equal`.
Ref: https://github.com/seattlerb/minitest/commit/922bc9151a622cb3ef0b9f170aa09c3bb72c7eb8
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Remove extra empty line
|
| | |/ / / /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Improve bundler binstub error message
|
| | | | | | | |
|
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Rails displays an error message if you have a bundler-generated binstub
at `./bin/rails` instead of a Rails-generated binstub.
This error message is misleading because it makes it seem as though
Rails 5 introduced recent changes in how binstubs are used, when these
changes were actually introduced way back in Rails 4.
The suggested upgrade steps are appropriate for an app that was created
in Rails 3, but they likely aren't the correct fix for someone who sees
this error message today on a modern app. I believe the `--binstubs`
option on bundler is a more likely culprit and troubleshooting path.
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
Handling add/remove to/from migration edge cases
|