diff options
| author | yuuji.yaginuma <yuuji.yaginuma@gmail.com> | 2019-06-29 08:43:16 +0900 |
|---|---|---|
| committer | yuuji.yaginuma <yuuji.yaginuma@gmail.com> | 2019-07-05 18:55:47 +0900 |
| commit | 6fec4c3a0aea3ef783372c55aff6d3c1efd89c4e (patch) | |
| tree | 54b17269751d4f5967fe335f617f1fdcf1cf685b /actionpack/test/controller/force_ssl_test.rb | |
| parent | a59b2305792dd7012a8abc2e4b1a7d9037e8e208 (diff) | |
| download | rails-6fec4c3a0aea3ef783372c55aff6d3c1efd89c4e.tar.gz rails-6fec4c3a0aea3ef783372c55aff6d3c1efd89c4e.tar.bz2 rails-6fec4c3a0aea3ef783372c55aff6d3c1efd89c4e.zip | |
Add `skip-collision-check` option to generator
Until Rails 5.2, generators can run same name multi times without destroying.
But Rails 6.0(with Zeitwerk) can't this. In Rails 6.0, an error occurs
due to class name collision check.
The check uses `const_defined?`, which assumes that the autoload object
is also defined.
https://ruby-doc.org/core-2.6.3/Module.html#method-i-const_defined-3F
It did not work until Rails 5.2, but Zeitwerk seems to be able to
correctly check this against the application's code.
However, this is a little inconvenient if want to run the generator
again like mistake an attribute name(need to run `destoy` before).
In order to solve this, this PR adds an option to skip the collision check.
With this option, you can overwrite files just as did until Rails 5.2.
Diffstat (limited to 'actionpack/test/controller/force_ssl_test.rb')
0 files changed, 0 insertions, 0 deletions