| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
| | | |
|
| |/ |
|
|\ \
| |/
|/| |
Show minitest options in test runner help
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since #29572, minitest options are available but are no longer showed
in help.
This fixed to show minitest option in help as with Rails 5.1.2.
**before**
```
./bin/rails t --help
You can run a single test by appending a line number to a filename:
bin/rails test test/models/user_test.rb:27
You can run multiple files and directories at the same time:
bin/rails test test/controllers test/integration/login_test.rb
By default test failures and errors are reported inline during a run.
Rails options:
-w, --warnings Run with Ruby warnings enabled
-e, --environment Run tests in the ENV environment
-b, --backtrace Show the complete backtrace
-d, --defer-output Output test failures and errors after the test run
-f, --fail-fast Abort test run on first failure or error
-c, --[no-]color Enable color in the output
```
**after**
```
./bin/rails t --help
You can run a single test by appending a line number to a filename:
bin/rails test test/models/user_test.rb:27
You can run multiple files and directories at the same time:
bin/rails test test/controllers test/integration/login_test.rb
By default test failures and errors are reported inline during a run.
minitest options:
-h, --help Display this help.
-s, --seed SEED Sets random seed. Also via env. Eg: SEED=n rake
-v, --verbose Verbose. Show progress processing files.
-n, --name PATTERN Filter run on /regexp/ or string.
--exclude PATTERN Exclude /regexp/ or string from run.
Known extensions: rails, pride
-w, --warnings Run with Ruby warnings enabled
-e, --environment Run tests in the ENV environment
-b, --backtrace Show the complete backtrace
-d, --defer-output Output test failures and errors after the test run
-f, --fail-fast Abort test run on first failure or error
-c, --[no-]color Enable color in the output
-p, --pride Pride. Show your testing pride!
```
|
|\ \
| | |
| | |
| | | |
Optimize indentation for generator actions
|
| | | |
|
|\ \ \
| | | |
| | | | |
Eager load controller actions to reduce response time of the first request
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On the first request, ActionController::Base#action_methods computes
and memoized the list of available actions [1]. With this PR we move
this expensive operation into eager load step to reduce response time
of the first request served in production.
This also reduces the memory footprint when running on forking server
like Unicorn.
[1] https://github.com/rails/rails/blob/a3813dce9a0c950a4af7909111fa730a2622b1db/actionpack/lib/abstract_controller/base.rb#L66-L77
|
|\ \ \
| | | |
| | | | |
Removed empty line from dummy_manifest
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
yhirano55/skip_unused_components_when_running_rails_command_in_plugin
Skip unused components when running `bin/rails` in Rails plugin
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Remove :sorted test order for isolated tests
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
Add git_source to Gemfile for plugin generator
|
| | |/ / / /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Prevent generation extra empty lines in a plugin's Rakefile
|
| | | | | | | |
|
| |_|_|_|_|/
|/| | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Improve app generator tests.
Ensure that generation `config/application.rb` is correct.
Ensure that generation `config/application.rb` is correct.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
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
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
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.
|