| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
yhirano55/skip_unused_components_when_running_rails_command_in_plugin
Skip unused components when running `bin/rails` in Rails plugin
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
Add git_source to Gemfile for plugin generator
|
| |/ / / / |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
Prevent generation extra empty lines in a plugin's Rakefile
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix engine command
|
| |/ / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
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
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
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
|
| |/ / / |
|
|/ / / |
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
Add Active Storage to Rails
|
| | |
| | |
| | |
| | | |
And deal with a temporary test fix until we allow you to skip active storage.
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Use duktape gem as default JS engine on Windows-MINGW
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
The fallback javascript engine on Windows is Windows Script Host (JScript).
However this engine isn't able to process the default assets, because it supports
ES3 only but the coffeescript compiler requires ES5.
Fixes #30014
|
|\ \ \
| | | |
| | | | |
Remove unnecessary `doc` directory deletion
|
| | |/
| |/|
| | |
| | | |
Since 553b695, `doc` directory is not created in application.
|
|\ \ \
| | | |
| | | | |
[ci skip] Fix rails_command comments
|
| | |/
| |/| |
|
| |/
|/| |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When generating models, we created ApplicationRecord in the default
location if no file existed there. That was annoying for people who
moved it to somewhere else in the autoload path. At this point, the
vast majority of apps should have either run the upgrade script or
generated a model since upgrading. For those that haven't the error
message after generating a new model should be helpful:
NameError: uninitialized constant ApplicationRecord
To ease friction in that case, this also adds a generator for
ApplicationRecord.
|
|
|
|
|
|
|
| |
Generators need to be aware of namespace to work properly in engines.
Methods to help with this lived in Rails::Generators::NamedBase. Moving
them to Rails::Generators::Base (which NamedBase inherits from) allows a
follow-up in which a namespace aware unnamed generator can be created.
|
|
|
|
|
|
| |
Bootsnap precomputes load path resolution and caches ruby ISeq
and YAML parsing/compilation, reducing application boot time by
approximately 50% on supported configurations.
|
| |
|
|\
| |
| | |
Do not generate unused components contents in `app:update` task
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, `app:update` generates all contents regardless of the
component using in application.
For example, even if not using Action Cable, `app:update` will generate
a contents related to Action Cable. This is a little inconvenient.
This PR checks the existence of the component and does not generate
unnecessary contents.
Can not check all options in this way. However, it will be able to
prevent the generation of unnecessary files.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Abstract boolean serialization has been using 't' and 'f', with MySQL
overriding that to use 1 and 0.
This has the advantage that SQLite natively recognizes 1 and 0 as true
and false, but does not natively recognize 't' and 'f'.
This change in serialization requires a migration of stored boolean data
for SQLite databases, so it's implemented behind a configuration flag
whose default false value is deprecated. The flag itself can be
deprecated in a future version of Rails. While loaded models will give
the correct result for boolean columns without migrating old data,
where() clauses will interact incorrectly with old data.
While working in this area, also change the abstract adapter to use
`"TRUE"` and `"FALSE"` as quoted values and `true` and `false` for
unquoted. These are supported by PostreSQL, and MySQL remains
overriden.
|