diff options
| author | Genadi Samokovarov <gsamokovarov@gmail.com> | 2016-04-27 18:30:17 +0300 |
|---|---|---|
| committer | Genadi Samokovarov <gsamokovarov@gmail.com> | 2016-04-28 10:12:06 +0300 |
| commit | e6ed3aaf437887bc25a1f715f21c5ca3ebbc966f (patch) | |
| tree | 8b24be4de8e045828209d724e1a6402028e4b907 /activerecord/test/cases/connection_specification/resolver_test.rb | |
| parent | abff83e60e9d91975b4788ef9cca388ab2536c10 (diff) | |
| download | rails-e6ed3aaf437887bc25a1f715f21c5ca3ebbc966f.tar.gz rails-e6ed3aaf437887bc25a1f715f21c5ca3ebbc966f.tar.bz2 rails-e6ed3aaf437887bc25a1f715f21c5ca3ebbc966f.zip | |
Always genererate models with ApplicationRecord parent
Currently, if we generate a model while
`app/model/application_record.rb` isn't present, we'll end up with a
model with an `ActiveRecord::Base` parent _and_ a newly generated
`app/models/application_record.rb`.
While the behavior for choosing an `ActiveRecord::Base` was chosen for
an easier migration math to 5.0, generating the
`app/model/application_record.rb` file kinda contradicts with it.
In any case, I think we should decide on a behavior and stick to it.
Here, I'm changing the generated parent to always be `ApplicationRecord`
and to always create `app/model/application_record.rb` if it doesn't
exist.
Diffstat (limited to 'activerecord/test/cases/connection_specification/resolver_test.rb')
0 files changed, 0 insertions, 0 deletions