| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Allow Minitest to load plugins. Fixes #21102
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
manifest file [ci skip]
use it
change the warning
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 465f0fbca3d4a1c269038b84ec9cc248fdab5fab.
This breaks some cases where non file / directory arguments are passed
to the runner (for example db:migrate).
I still think that we can get this to work. From what I can tell there
is no reason why db:migrate is passed along to `Minitest.run`. I'll
revert and investigate possible solutions.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Inform user to add styles in correct location in application.css
[ci skip]
|
| |/ |
|
|/
|
|
|
|
|
|
| |
Before this patch, using `bin/rails test` with a non existing
file or directory argument would silently swallow the argument and
run the whole test suite.
After the patch the command fails with `cannot load such file --`.
|
|\
| |
| | |
Don't fail when checking dependencies in bin/setup script
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Presumably due to https://github.com/rails/sprockets-rails/pull/265 sprockets was trying to load the "scss" gem but it isn't in the gemfile:
```
ApplicationTests::RakeTests::RakeNotesTest#test_register_a_new_extension:
LoadError: cannot load such file -- sass
```
If we use an empty precompile list, it won't try to load sass.
|
| |
| |
| |
| | |
We can prevent the UglifierCompressor from being instantiated prematurely by setting precompile to an empty array in this test.
|
| | |
|
|\ \
| | |
| | | |
Change wrong usage in documentation about autoload_paths [ci skip]
|
| | |
| | |
| | |
| | | |
We can't use this configuration outside of the application.rb
|
|\ \ \
| | | |
| | | | |
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
|
| | |
|
|/ |
|
| |
|