2014-05-23 14:24:52 -04:00
|
|
|
require 'cases/helper'
|
|
|
|
|
|
|
|
class OverloadedType < ActiveRecord::Base
|
2015-02-06 13:05:38 -05:00
|
|
|
attribute :overloaded_float, :integer
|
|
|
|
attribute :overloaded_string_with_limit, :string, limit: 50
|
|
|
|
attribute :non_existent_decimal, :decimal
|
|
|
|
attribute :string_with_default, :string, default: 'the overloaded default'
|
2014-05-23 14:24:52 -04:00
|
|
|
end
|
|
|
|
|
2014-05-28 13:11:57 -04:00
|
|
|
class ChildOfOverloadedType < OverloadedType
|
|
|
|
end
|
|
|
|
|
|
|
|
class GrandchildOfOverloadedType < ChildOfOverloadedType
|
2015-02-06 13:05:38 -05:00
|
|
|
attribute :overloaded_float, :float
|
2014-05-28 13:11:57 -04:00
|
|
|
end
|
|
|
|
|
2014-05-23 14:24:52 -04:00
|
|
|
class UnoverloadedType < ActiveRecord::Base
|
|
|
|
self.table_name = 'overloaded_types'
|
|
|
|
end
|
|
|
|
|
|
|
|
module ActiveRecord
|
|
|
|
class CustomPropertiesTest < ActiveRecord::TestCase
|
2014-10-31 18:06:14 -04:00
|
|
|
test "overloading types" do
|
2014-05-23 14:24:52 -04:00
|
|
|
data = OverloadedType.new
|
|
|
|
|
|
|
|
data.overloaded_float = "1.1"
|
|
|
|
data.unoverloaded_float = "1.1"
|
|
|
|
|
|
|
|
assert_equal 1, data.overloaded_float
|
|
|
|
assert_equal 1.1, data.unoverloaded_float
|
|
|
|
end
|
|
|
|
|
2014-10-31 18:06:14 -04:00
|
|
|
test "overloaded properties save" do
|
2014-05-23 14:24:52 -04:00
|
|
|
data = OverloadedType.new
|
|
|
|
|
|
|
|
data.overloaded_float = "2.2"
|
|
|
|
data.save!
|
|
|
|
data.reload
|
|
|
|
|
|
|
|
assert_equal 2, data.overloaded_float
|
2014-05-29 09:55:44 -04:00
|
|
|
assert_kind_of Fixnum, OverloadedType.last.overloaded_float
|
2014-05-23 14:24:52 -04:00
|
|
|
assert_equal 2.0, UnoverloadedType.last.overloaded_float
|
2014-05-29 09:55:44 -04:00
|
|
|
assert_kind_of Float, UnoverloadedType.last.overloaded_float
|
2014-05-23 14:24:52 -04:00
|
|
|
end
|
|
|
|
|
2014-10-31 18:06:14 -04:00
|
|
|
test "properties assigned in constructor" do
|
2014-05-23 14:24:52 -04:00
|
|
|
data = OverloadedType.new(overloaded_float: '3.3')
|
|
|
|
|
|
|
|
assert_equal 3, data.overloaded_float
|
|
|
|
end
|
|
|
|
|
2014-10-31 18:06:14 -04:00
|
|
|
test "overloaded properties with limit" do
|
Attribute assignment and type casting has nothing to do with columns
It's finally finished!!!!!!! The reason the Attributes API was kept
private in 4.2 was due to some publicly visible implementation details.
It was previously implemented by overloading `columns` and
`columns_hash`, to make them return column objects which were modified
with the attribute information.
This meant that those methods LIED! We didn't change the database
schema. We changed the attribute information on the class. That is
wrong! It should be the other way around, where schema loading just
calls the attributes API for you. And now it does!
Yes, this means that there is nothing that happens in automatic schema
loading that you couldn't manually do yourself. (There's still some
funky cases where we hit the connection adapter that I need to handle,
before we can turn off automatic schema detection entirely.)
There were a few weird test failures caused by this that had to be
fixed. The main source came from the fact that the attribute methods are
now defined in terms of `attribute_names`, which has a clause like
`return [] unless table_exists?`. I don't *think* this is an issue,
since the only place this caused failures were in a fake adapter which
didn't override `table_exists?`.
Additionally, there were a few cases where tests were failing because a
migration was run, but the model was not reloaded. I'm not sure why
these started failing from this change, I might need to clear an
additional cache in `reload_schema_from_cache`. Again, since this is not
normal usage, and it's expected that `reset_column_information` will be
called after the table is modified, I don't think it's a problem.
Still, test failures that were unrelated to the change are worrying, and
I need to dig into them further.
Finally, I spent a lot of time debugging issues with the mutex used in
`define_attribute_methods`. I think we can just remove that method
entirely, and define the attribute methods *manually* in the call to
`define_attribute`, which would simplify the code *tremendously*.
Ok. now to make this damn thing public, and work on moving it up to
Active Model.
2015-01-30 16:03:36 -05:00
|
|
|
assert_equal 50, OverloadedType.type_for_attribute('overloaded_string_with_limit').limit
|
|
|
|
assert_equal 255, UnoverloadedType.type_for_attribute('overloaded_string_with_limit').limit
|
2014-05-23 14:24:52 -04:00
|
|
|
end
|
|
|
|
|
2014-10-31 18:06:14 -04:00
|
|
|
test "nonexistent attribute" do
|
2014-05-23 14:24:52 -04:00
|
|
|
data = OverloadedType.new(non_existent_decimal: 1)
|
|
|
|
|
|
|
|
assert_equal BigDecimal.new(1), data.non_existent_decimal
|
2015-02-25 09:14:43 -05:00
|
|
|
assert_raise ActiveRecord::UnknownAttributeError do
|
2014-05-23 14:24:52 -04:00
|
|
|
UnoverloadedType.new(non_existent_decimal: 1)
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2014-10-31 18:06:14 -04:00
|
|
|
test "changing defaults" do
|
2014-05-23 14:24:52 -04:00
|
|
|
data = OverloadedType.new
|
|
|
|
unoverloaded_data = UnoverloadedType.new
|
|
|
|
|
2014-05-26 20:06:05 -04:00
|
|
|
assert_equal 'the overloaded default', data.string_with_default
|
|
|
|
assert_equal 'the original default', unoverloaded_data.string_with_default
|
2014-05-23 14:24:52 -04:00
|
|
|
end
|
2014-05-28 13:11:57 -04:00
|
|
|
|
2014-10-31 18:06:14 -04:00
|
|
|
test "defaults are not touched on the columns" do
|
|
|
|
assert_equal 'the original default', OverloadedType.columns_hash['string_with_default'].default
|
|
|
|
end
|
|
|
|
|
|
|
|
test "children inherit custom properties" do
|
2014-05-28 13:11:57 -04:00
|
|
|
data = ChildOfOverloadedType.new(overloaded_float: '4.4')
|
|
|
|
|
|
|
|
assert_equal 4, data.overloaded_float
|
|
|
|
end
|
|
|
|
|
2014-10-31 18:06:14 -04:00
|
|
|
test "children can override parents" do
|
2014-05-28 13:11:57 -04:00
|
|
|
data = GrandchildOfOverloadedType.new(overloaded_float: '4.4')
|
|
|
|
|
|
|
|
assert_equal 4.4, data.overloaded_float
|
|
|
|
end
|
2014-05-28 13:32:00 -04:00
|
|
|
|
Attribute assignment and type casting has nothing to do with columns
It's finally finished!!!!!!! The reason the Attributes API was kept
private in 4.2 was due to some publicly visible implementation details.
It was previously implemented by overloading `columns` and
`columns_hash`, to make them return column objects which were modified
with the attribute information.
This meant that those methods LIED! We didn't change the database
schema. We changed the attribute information on the class. That is
wrong! It should be the other way around, where schema loading just
calls the attributes API for you. And now it does!
Yes, this means that there is nothing that happens in automatic schema
loading that you couldn't manually do yourself. (There's still some
funky cases where we hit the connection adapter that I need to handle,
before we can turn off automatic schema detection entirely.)
There were a few weird test failures caused by this that had to be
fixed. The main source came from the fact that the attribute methods are
now defined in terms of `attribute_names`, which has a clause like
`return [] unless table_exists?`. I don't *think* this is an issue,
since the only place this caused failures were in a fake adapter which
didn't override `table_exists?`.
Additionally, there were a few cases where tests were failing because a
migration was run, but the model was not reloaded. I'm not sure why
these started failing from this change, I might need to clear an
additional cache in `reload_schema_from_cache`. Again, since this is not
normal usage, and it's expected that `reset_column_information` will be
called after the table is modified, I don't think it's a problem.
Still, test failures that were unrelated to the change are worrying, and
I need to dig into them further.
Finally, I spent a lot of time debugging issues with the mutex used in
`define_attribute_methods`. I think we can just remove that method
entirely, and define the attribute methods *manually* in the call to
`define_attribute`, which would simplify the code *tremendously*.
Ok. now to make this damn thing public, and work on moving it up to
Active Model.
2015-01-30 16:03:36 -05:00
|
|
|
test "overloading properties does not attribute method order" do
|
|
|
|
attribute_names = OverloadedType.attribute_names
|
|
|
|
assert_equal %w(id overloaded_float unoverloaded_float overloaded_string_with_limit string_with_default non_existent_decimal), attribute_names
|
2014-05-28 13:32:00 -04:00
|
|
|
end
|
2014-05-30 16:51:27 -04:00
|
|
|
|
2014-10-31 18:06:14 -04:00
|
|
|
test "caches are cleared" do
|
2014-05-30 16:51:27 -04:00
|
|
|
klass = Class.new(OverloadedType)
|
|
|
|
|
Attribute assignment and type casting has nothing to do with columns
It's finally finished!!!!!!! The reason the Attributes API was kept
private in 4.2 was due to some publicly visible implementation details.
It was previously implemented by overloading `columns` and
`columns_hash`, to make them return column objects which were modified
with the attribute information.
This meant that those methods LIED! We didn't change the database
schema. We changed the attribute information on the class. That is
wrong! It should be the other way around, where schema loading just
calls the attributes API for you. And now it does!
Yes, this means that there is nothing that happens in automatic schema
loading that you couldn't manually do yourself. (There's still some
funky cases where we hit the connection adapter that I need to handle,
before we can turn off automatic schema detection entirely.)
There were a few weird test failures caused by this that had to be
fixed. The main source came from the fact that the attribute methods are
now defined in terms of `attribute_names`, which has a clause like
`return [] unless table_exists?`. I don't *think* this is an issue,
since the only place this caused failures were in a fake adapter which
didn't override `table_exists?`.
Additionally, there were a few cases where tests were failing because a
migration was run, but the model was not reloaded. I'm not sure why
these started failing from this change, I might need to clear an
additional cache in `reload_schema_from_cache`. Again, since this is not
normal usage, and it's expected that `reset_column_information` will be
called after the table is modified, I don't think it's a problem.
Still, test failures that were unrelated to the change are worrying, and
I need to dig into them further.
Finally, I spent a lot of time debugging issues with the mutex used in
`define_attribute_methods`. I think we can just remove that method
entirely, and define the attribute methods *manually* in the call to
`define_attribute`, which would simplify the code *tremendously*.
Ok. now to make this damn thing public, and work on moving it up to
Active Model.
2015-01-30 16:03:36 -05:00
|
|
|
assert_equal 6, klass.attribute_types.length
|
2014-05-30 16:51:27 -04:00
|
|
|
assert_equal 6, klass.column_defaults.length
|
Attribute assignment and type casting has nothing to do with columns
It's finally finished!!!!!!! The reason the Attributes API was kept
private in 4.2 was due to some publicly visible implementation details.
It was previously implemented by overloading `columns` and
`columns_hash`, to make them return column objects which were modified
with the attribute information.
This meant that those methods LIED! We didn't change the database
schema. We changed the attribute information on the class. That is
wrong! It should be the other way around, where schema loading just
calls the attributes API for you. And now it does!
Yes, this means that there is nothing that happens in automatic schema
loading that you couldn't manually do yourself. (There's still some
funky cases where we hit the connection adapter that I need to handle,
before we can turn off automatic schema detection entirely.)
There were a few weird test failures caused by this that had to be
fixed. The main source came from the fact that the attribute methods are
now defined in terms of `attribute_names`, which has a clause like
`return [] unless table_exists?`. I don't *think* this is an issue,
since the only place this caused failures were in a fake adapter which
didn't override `table_exists?`.
Additionally, there were a few cases where tests were failing because a
migration was run, but the model was not reloaded. I'm not sure why
these started failing from this change, I might need to clear an
additional cache in `reload_schema_from_cache`. Again, since this is not
normal usage, and it's expected that `reset_column_information` will be
called after the table is modified, I don't think it's a problem.
Still, test failures that were unrelated to the change are worrying, and
I need to dig into them further.
Finally, I spent a lot of time debugging issues with the mutex used in
`define_attribute_methods`. I think we can just remove that method
entirely, and define the attribute methods *manually* in the call to
`define_attribute`, which would simplify the code *tremendously*.
Ok. now to make this damn thing public, and work on moving it up to
Active Model.
2015-01-30 16:03:36 -05:00
|
|
|
assert_not klass.attribute_types.include?('wibble')
|
2014-05-30 16:51:27 -04:00
|
|
|
|
2014-06-07 09:09:45 -04:00
|
|
|
klass.attribute :wibble, Type::Value.new
|
2014-05-30 16:51:27 -04:00
|
|
|
|
Attribute assignment and type casting has nothing to do with columns
It's finally finished!!!!!!! The reason the Attributes API was kept
private in 4.2 was due to some publicly visible implementation details.
It was previously implemented by overloading `columns` and
`columns_hash`, to make them return column objects which were modified
with the attribute information.
This meant that those methods LIED! We didn't change the database
schema. We changed the attribute information on the class. That is
wrong! It should be the other way around, where schema loading just
calls the attributes API for you. And now it does!
Yes, this means that there is nothing that happens in automatic schema
loading that you couldn't manually do yourself. (There's still some
funky cases where we hit the connection adapter that I need to handle,
before we can turn off automatic schema detection entirely.)
There were a few weird test failures caused by this that had to be
fixed. The main source came from the fact that the attribute methods are
now defined in terms of `attribute_names`, which has a clause like
`return [] unless table_exists?`. I don't *think* this is an issue,
since the only place this caused failures were in a fake adapter which
didn't override `table_exists?`.
Additionally, there were a few cases where tests were failing because a
migration was run, but the model was not reloaded. I'm not sure why
these started failing from this change, I might need to clear an
additional cache in `reload_schema_from_cache`. Again, since this is not
normal usage, and it's expected that `reset_column_information` will be
called after the table is modified, I don't think it's a problem.
Still, test failures that were unrelated to the change are worrying, and
I need to dig into them further.
Finally, I spent a lot of time debugging issues with the mutex used in
`define_attribute_methods`. I think we can just remove that method
entirely, and define the attribute methods *manually* in the call to
`define_attribute`, which would simplify the code *tremendously*.
Ok. now to make this damn thing public, and work on moving it up to
Active Model.
2015-01-30 16:03:36 -05:00
|
|
|
assert_equal 7, klass.attribute_types.length
|
2014-05-30 16:51:27 -04:00
|
|
|
assert_equal 7, klass.column_defaults.length
|
Attribute assignment and type casting has nothing to do with columns
It's finally finished!!!!!!! The reason the Attributes API was kept
private in 4.2 was due to some publicly visible implementation details.
It was previously implemented by overloading `columns` and
`columns_hash`, to make them return column objects which were modified
with the attribute information.
This meant that those methods LIED! We didn't change the database
schema. We changed the attribute information on the class. That is
wrong! It should be the other way around, where schema loading just
calls the attributes API for you. And now it does!
Yes, this means that there is nothing that happens in automatic schema
loading that you couldn't manually do yourself. (There's still some
funky cases where we hit the connection adapter that I need to handle,
before we can turn off automatic schema detection entirely.)
There were a few weird test failures caused by this that had to be
fixed. The main source came from the fact that the attribute methods are
now defined in terms of `attribute_names`, which has a clause like
`return [] unless table_exists?`. I don't *think* this is an issue,
since the only place this caused failures were in a fake adapter which
didn't override `table_exists?`.
Additionally, there were a few cases where tests were failing because a
migration was run, but the model was not reloaded. I'm not sure why
these started failing from this change, I might need to clear an
additional cache in `reload_schema_from_cache`. Again, since this is not
normal usage, and it's expected that `reset_column_information` will be
called after the table is modified, I don't think it's a problem.
Still, test failures that were unrelated to the change are worrying, and
I need to dig into them further.
Finally, I spent a lot of time debugging issues with the mutex used in
`define_attribute_methods`. I think we can just remove that method
entirely, and define the attribute methods *manually* in the call to
`define_attribute`, which would simplify the code *tremendously*.
Ok. now to make this damn thing public, and work on moving it up to
Active Model.
2015-01-30 16:03:36 -05:00
|
|
|
assert klass.attribute_types.include?('wibble')
|
|
|
|
end
|
|
|
|
|
|
|
|
test "the given default value is cast from user" do
|
|
|
|
custom_type = Class.new(Type::Value) do
|
2015-02-17 15:39:42 -05:00
|
|
|
def cast(*)
|
Attribute assignment and type casting has nothing to do with columns
It's finally finished!!!!!!! The reason the Attributes API was kept
private in 4.2 was due to some publicly visible implementation details.
It was previously implemented by overloading `columns` and
`columns_hash`, to make them return column objects which were modified
with the attribute information.
This meant that those methods LIED! We didn't change the database
schema. We changed the attribute information on the class. That is
wrong! It should be the other way around, where schema loading just
calls the attributes API for you. And now it does!
Yes, this means that there is nothing that happens in automatic schema
loading that you couldn't manually do yourself. (There's still some
funky cases where we hit the connection adapter that I need to handle,
before we can turn off automatic schema detection entirely.)
There were a few weird test failures caused by this that had to be
fixed. The main source came from the fact that the attribute methods are
now defined in terms of `attribute_names`, which has a clause like
`return [] unless table_exists?`. I don't *think* this is an issue,
since the only place this caused failures were in a fake adapter which
didn't override `table_exists?`.
Additionally, there were a few cases where tests were failing because a
migration was run, but the model was not reloaded. I'm not sure why
these started failing from this change, I might need to clear an
additional cache in `reload_schema_from_cache`. Again, since this is not
normal usage, and it's expected that `reset_column_information` will be
called after the table is modified, I don't think it's a problem.
Still, test failures that were unrelated to the change are worrying, and
I need to dig into them further.
Finally, I spent a lot of time debugging issues with the mutex used in
`define_attribute_methods`. I think we can just remove that method
entirely, and define the attribute methods *manually* in the call to
`define_attribute`, which would simplify the code *tremendously*.
Ok. now to make this damn thing public, and work on moving it up to
Active Model.
2015-01-30 16:03:36 -05:00
|
|
|
"from user"
|
|
|
|
end
|
|
|
|
|
2015-02-17 13:29:51 -05:00
|
|
|
def deserialize(*)
|
Attribute assignment and type casting has nothing to do with columns
It's finally finished!!!!!!! The reason the Attributes API was kept
private in 4.2 was due to some publicly visible implementation details.
It was previously implemented by overloading `columns` and
`columns_hash`, to make them return column objects which were modified
with the attribute information.
This meant that those methods LIED! We didn't change the database
schema. We changed the attribute information on the class. That is
wrong! It should be the other way around, where schema loading just
calls the attributes API for you. And now it does!
Yes, this means that there is nothing that happens in automatic schema
loading that you couldn't manually do yourself. (There's still some
funky cases where we hit the connection adapter that I need to handle,
before we can turn off automatic schema detection entirely.)
There were a few weird test failures caused by this that had to be
fixed. The main source came from the fact that the attribute methods are
now defined in terms of `attribute_names`, which has a clause like
`return [] unless table_exists?`. I don't *think* this is an issue,
since the only place this caused failures were in a fake adapter which
didn't override `table_exists?`.
Additionally, there were a few cases where tests were failing because a
migration was run, but the model was not reloaded. I'm not sure why
these started failing from this change, I might need to clear an
additional cache in `reload_schema_from_cache`. Again, since this is not
normal usage, and it's expected that `reset_column_information` will be
called after the table is modified, I don't think it's a problem.
Still, test failures that were unrelated to the change are worrying, and
I need to dig into them further.
Finally, I spent a lot of time debugging issues with the mutex used in
`define_attribute_methods`. I think we can just remove that method
entirely, and define the attribute methods *manually* in the call to
`define_attribute`, which would simplify the code *tremendously*.
Ok. now to make this damn thing public, and work on moving it up to
Active Model.
2015-01-30 16:03:36 -05:00
|
|
|
"from database"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
klass = Class.new(OverloadedType) do
|
|
|
|
attribute :wibble, custom_type.new, default: "default"
|
|
|
|
end
|
|
|
|
model = klass.new
|
|
|
|
|
|
|
|
assert_equal "from user", model.wibble
|
2014-05-30 16:51:27 -04:00
|
|
|
end
|
2015-02-06 13:05:38 -05:00
|
|
|
|
2015-05-28 18:26:49 -04:00
|
|
|
test "procs for default values" do
|
|
|
|
klass = Class.new(OverloadedType) do
|
|
|
|
@@counter = 0
|
|
|
|
attribute :counter, :integer, default: -> { @@counter += 1 }
|
|
|
|
end
|
|
|
|
|
|
|
|
assert_equal 1, klass.new.counter
|
|
|
|
assert_equal 2, klass.new.counter
|
|
|
|
end
|
|
|
|
|
Persist user provided default values, even if unchanged
This is a usability change to fix a quirk from our definition of partial
writes. By default, we only persist changed attributes. When creating a
new record, this is assumed that the default values came from the
database. However, if the user provided a default, it will not be
persisted, since we didn't see it as "changed". Since this is a very
specific case, I wanted to isolate it with the other quirks that come
from user provided default values. The number of edge cases which are
presenting themselves are starting to make me wonder if we should just
remove the ability to assign a default, in favor of overriding
`initialize`. For the time being, this is required for the attributes
API to not have confusing behavior.
We had to delete one test, since this actually changes the meaning of
`.changed?` on Active Record models. It now specifically means
`changed_from_database?`. While I think this will make the attributes
API more ergonomic to use, it is a subtle change in definition (though
not a backwards incompatible one). We should probably figure out the
right place to document this. (Feel free to open a PR doing that if
you're reading this).
/cc @rafaelfranca @kirs @senny
This is an alternate implementation of #19921.
Close #19921.
[Sean Griffin & Kir Shatrov]
2015-05-28 18:33:38 -04:00
|
|
|
test "user provided defaults are persisted even if unchanged" do
|
|
|
|
model = OverloadedType.create!
|
|
|
|
|
|
|
|
assert_equal "the overloaded default", model.reload.string_with_default
|
|
|
|
end
|
|
|
|
|
2015-02-06 13:05:38 -05:00
|
|
|
if current_adapter?(:PostgreSQLAdapter)
|
2015-07-20 11:22:30 -04:00
|
|
|
test "array types can be specified" do
|
2015-02-06 13:05:38 -05:00
|
|
|
klass = Class.new(OverloadedType) do
|
|
|
|
attribute :my_array, :string, limit: 50, array: true
|
|
|
|
attribute :my_int_array, :integer, array: true
|
|
|
|
end
|
|
|
|
|
|
|
|
string_array = ConnectionAdapters::PostgreSQL::OID::Array.new(
|
|
|
|
Type::String.new(limit: 50))
|
|
|
|
int_array = ConnectionAdapters::PostgreSQL::OID::Array.new(
|
|
|
|
Type::Integer.new)
|
2015-08-13 03:20:39 -04:00
|
|
|
assert_not_equal string_array, int_array
|
2015-02-06 13:05:38 -05:00
|
|
|
assert_equal string_array, klass.type_for_attribute("my_array")
|
|
|
|
assert_equal int_array, klass.type_for_attribute("my_int_array")
|
|
|
|
end
|
|
|
|
|
|
|
|
test "range types can be specified" do
|
|
|
|
klass = Class.new(OverloadedType) do
|
|
|
|
attribute :my_range, :string, limit: 50, range: true
|
|
|
|
attribute :my_int_range, :integer, range: true
|
|
|
|
end
|
|
|
|
|
|
|
|
string_range = ConnectionAdapters::PostgreSQL::OID::Range.new(
|
|
|
|
Type::String.new(limit: 50))
|
|
|
|
int_range = ConnectionAdapters::PostgreSQL::OID::Range.new(
|
|
|
|
Type::Integer.new)
|
2015-08-13 03:20:39 -04:00
|
|
|
assert_not_equal string_range, int_range
|
2015-02-06 13:05:38 -05:00
|
|
|
assert_equal string_range, klass.type_for_attribute("my_range")
|
|
|
|
assert_equal int_range, klass.type_for_attribute("my_int_range")
|
|
|
|
end
|
|
|
|
end
|
2015-11-07 10:17:25 -05:00
|
|
|
|
|
|
|
test "attributes added after subclasses load are inherited" do
|
|
|
|
parent = Class.new(ActiveRecord::Base) do
|
|
|
|
self.table_name = "topics"
|
|
|
|
end
|
|
|
|
|
|
|
|
child = Class.new(parent)
|
|
|
|
child.new # => force a schema load
|
|
|
|
|
|
|
|
parent.attribute(:foo, Type::Value.new)
|
|
|
|
|
|
|
|
assert_equal(:bar, child.new(foo: :bar).foo)
|
|
|
|
end
|
2014-05-23 14:24:52 -04:00
|
|
|
end
|
|
|
|
end
|