diff options
| author | Lisa Ugray <lisa.ugray@shopify.com> | 2017-07-24 14:17:56 -0400 |
|---|---|---|
| committer | Lisa Ugray <lisa.ugray@shopify.com> | 2017-07-24 21:22:48 -0400 |
| commit | 75ccdfed8d43d79f6590653212ecea7124759439 (patch) | |
| tree | 3f0917b8813a7f6e05dd732306a759911d3ce4d2 /railties/test/generators_test.rb | |
| parent | 9c35bf2a6a27431c6aa283db781c19f61c5155be (diff) | |
| download | rails-75ccdfed8d43d79f6590653212ecea7124759439.tar.gz rails-75ccdfed8d43d79f6590653212ecea7124759439.tar.bz2 rails-75ccdfed8d43d79f6590653212ecea7124759439.zip | |
Stop creating ApplicationRecord on model generation
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.
Diffstat (limited to 'railties/test/generators_test.rb')
| -rw-r--r-- | railties/test/generators_test.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/test/generators_test.rb b/railties/test/generators_test.rb index e07627f36d..5063e864ca 100644 --- a/railties/test/generators_test.rb +++ b/railties/test/generators_test.rb @@ -124,7 +124,7 @@ class GeneratorsTest < Rails::Generators::TestCase def test_rails_generators_help_does_not_include_app_nor_plugin_new output = capture(:stdout) { Rails::Generators.help } - assert_no_match(/app/, output) + assert_no_match(/app\W/, output) assert_no_match(/[^:]plugin/, output) end |