| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | | |
Allow generating plugins for API applications
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This way, running a generator inside the plugin's directory, files that
are not relevant won't be generated (e.g. views or assets).
This won't interfere with the application's generators configuration.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | |/ / / /
| |/| | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
We need stricter locking before we can unload
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Specifically, the "loose upgrades" behaviour that allows us to obtain an
exclusive right to load things while other requests are in progress (but
waiting on the exclusive lock for themselves) prevents us from treating
load & unload interchangeably: new things appearing is fine, but they do
*not* expect previously-present constants to vanish.
We can still use loose upgrades for unloading -- once someone has
decided to unload, they don't really care if someone else gets there
first -- it just needs to be tracked separately.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
add system! to fail fast in bin/setup
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
remove `web-console` from API app generated Gemfile
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
Use digest cache in development.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Avoid computing the same fragment digest many times when looping over templates.
The cache is cleared on every request so template changes are still picked up.
|
| |_|_|_|/ /
|/| | | | |
| | | | | |
| | | | | | |
Various grammar corrections and wrap to 80 characters.
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
constant loading should be thread safe now, so lets remove this
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
We don't need to fully disable concurrent requests: just ensure that
loads are performed in isolation.
|
|\ \ \ \
| | | | |
| | | | | |
remove unnecessary loading fixtures from `navigation_test.rb`
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
it has been corrected in 0176aef1ebaa9f69001c7045a51727a8ea9b61b8 as for loading of fixtures in `test_helper.rb`,
loading fixtures for each test is unnecessary.
|
|/ / /
| | |
| | |
| | |
| | | |
Interpolating an array inside a String will call #inspect on it. Let's
call #join to display a more human-readable error message.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The improvments to the test runner's integration with minitest in commit
b6fc8e25a10cc4abdd03018798b180270d6c5d7f add methods to the Minitest
module that refer to the Rails module. Unfortunately, when the
minitest-rails gem is loaded, the reference is incorrectly resolved to
the Minitest::Rails module.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Closes #20743.
The task `db:_dump` now only dumps the schema if
`ActiveRecord::Base.dump_schema_after_migration` is true. This has
effects:
- `db:migrate:up`
- `db:migrate:down`
- `db:forward`
- `db:rollback`
|
| | |
| | |
| | |
| | |
| | | |
We recommend using the `bin/` executables in our docs and guides.
Let's make sure that our tests execute the same code path.
|
|\ \ \
| | | |
| | | |
| | | | |
fix NoMethodError that occurs when generating scaffold inside full mode engine
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Remove `config` options from `default_options` in `railties`
|
| | | |
| | | |
| | | |
| | | | |
Fixes #20345.
|
|\ \ \ \
| |/ / /
|/| | | |
correct `file_fixture_path` in plugins `test_helper.rb`
|
| | | |
| | | |
| | | |
| | | | |
`fixture_path` does not end with a slash
|
| | | | |
|
|/ / / |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
assert_file understands paths with special characters
|
| | | |
| | | |
| | | | |
fixes #20042
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
ContentLength is not part of the rack SPEC since rack/rack@86ddc7a6ec68d7b6951c2dbd07947c4254e8bc0d
If you want it, just add it as a middleware in your config.
|
|\ \ \ \
| | | | |
| | | | | |
Use single quote in Railties generators Gemfile [ci skip]
|
| |/ / / |
|
|/ / / |
|
|/ /
| |
| |
| |
| | |
Since #13612, `template` is no longer being used to generate
migrations.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the Rails repository we use a `bin/test` executable to run our tests.
However the rerun snippets still included `bin/rails test`:
BEFORE:
```
Failed tests:
bin/rails test test/cases/adapters/postgresql/schema_test.rb:91
```
AFTER:
```
Failed tests:
bin/test test/cases/adapters/postgresql/schema_test.rb:91
```
|
|\ \
| | |
| | | |
use our own runner for Rails framework components `bin/test`
|
| | |
| | |
| | |
| | |
| | | |
This makes it possible to easily get the runner working with existing
setups that rely on `active_support/testing/autorun.rb`.
|
| | |
| | |
| | |
| | | |
This looks to be just out of sync tests
|
| | | |
|
| | | |
|