diff options
| author | Sean Griffin <sean@seantheprogrammer.com> | 2015-09-21 09:40:04 -0600 |
|---|---|---|
| committer | Sean Griffin <sean@seantheprogrammer.com> | 2015-09-21 10:12:31 -0600 |
| commit | 4590d7729e241cb7f66e018a2a9759cb3baa36e5 (patch) | |
| tree | 9e2f5c0ba4547e08f58f0c137a698f035cfc2ad9 /actionpack/test/assertions | |
| parent | 22cc2b86f790b08bf58311bb6eb3bb148cb1dea9 (diff) | |
| download | rails-4590d7729e241cb7f66e018a2a9759cb3baa36e5.tar.gz rails-4590d7729e241cb7f66e018a2a9759cb3baa36e5.tar.bz2 rails-4590d7729e241cb7f66e018a2a9759cb3baa36e5.zip | |
Simplify the implementation of Active Model's type registry
Things like decorations, overrides, and priorities only matter for
Active Record, so the Active Model registry can be implemented much more
simply. At this point, I wonder if having Active Record's registry
inherit from Active Model's is even worth the trouble?
The Active Model class was also missing test cases, which have been
backfilled.
This removes the error when two types are registered with the same name,
but given that Active Model is meant to be significantly more generic, I
do not think this is an issue for now. If we want, we can raise an error
at the point that someone tries to register it.
Diffstat (limited to 'actionpack/test/assertions')
0 files changed, 0 insertions, 0 deletions