module ActiveRecord::AttributeMethods::TimeZoneConversion::ClassMethods
Private Instance Methods
create_time_zone_conversion_attribute?(name, cast_type)
click to toggle source
# File lib/active_record/attribute_methods/time_zone_conversion.rb, line 86 def create_time_zone_conversion_attribute?(name, cast_type) enabled_for_column = time_zone_aware_attributes && !self.skip_time_zone_conversion_for_attributes.include?(name.to_sym) result = enabled_for_column && time_zone_aware_types.include?(cast_type.type) if enabled_for_column && !result && cast_type.type == :time && time_zone_aware_types.include?(:not_explicitly_configured) ActiveSupport::Deprecation.warn(" Time columns will become time zone aware in Rails 5.1. This still causes `String`s to be parsed as if they were in `Time.zone`, and `Time`s to be converted to `Time.zone`. To keep the old behavior, you must add the following to your initializer: config.active_record.time_zone_aware_types = [:datetime] To silence this deprecation warning, add the following: config.active_record.time_zone_aware_types = [:datetime, :time] ".strip_heredoc) end result end
inherited(subclass)
click to toggle source
Calls superclass method
# File lib/active_record/attribute_methods/time_zone_conversion.rb, line 72 def inherited(subclass) # We need to apply this decorator here, rather than on module inclusion. The closure # created by the matcher would otherwise evaluate for `ActiveRecord::Base`, not the # sub class being decorated. As such, changes to `time_zone_aware_attributes`, or # `skip_time_zone_conversion_for_attributes` would not be picked up. subclass.class_eval do matcher = ->(name, type) { create_time_zone_conversion_attribute?(name, type) } decorate_matching_attribute_types(matcher, :_time_zone_conversion) do |type| TimeZoneConverter.new(type) end end super end