class PaperTrail::Events::Update
See docs in `Base`.
@api private
Public Class Methods
new(record, in_after_callback, is_touch, force_changes)
click to toggle source
-
is_touch - [boolean] - Used in the two situations that are touch-like:
-
`after_touch` we call `RecordTrail#record_update`
-
-
force_changes - [Hash] - Only used by `RecordTrail#update_columns`, because there dirty-tracking is off, so it has to track its own changes.
@api private
Calls superclass method
PaperTrail::Events::Base::new
# File lib/mongo_trails/events/update.rb, line 17 def initialize(record, in_after_callback, is_touch, force_changes) super(record, in_after_callback) @is_touch = is_touch @force_changes = force_changes end
Public Instance Methods
data()
click to toggle source
Return attributes of nascent `Version` record.
@api private
# File lib/mongo_trails/events/update.rb, line 26 def data data = { item: @record, event: @record.paper_trail_event || "update", whodunnit: PaperTrail.request.whodunnit } if @record.respond_to?(:updated_at) data[:created_at] = @record.updated_at end if record_object? data[:object] = recordable_object(@is_touch) end if record_object_changes? changes = @force_changes.nil? ? notable_changes : @force_changes data[:object_changes] = prepare_object_changes(changes) end merge_item_subtype_into(data) merge_metadata_into(data) end
Private Instance Methods
record_object_changes?()
click to toggle source
`touch` cannot record `object_changes` because rails' `touch` does not perform dirty-tracking. Specifically, methods from `Dirty`, like `saved_changes`, return the same values before and after `touch`.
See github.com/rails/rails/issues/33429
@api private
Calls superclass method
PaperTrail::Events::Base#record_object_changes?
# File lib/mongo_trails/events/update.rb, line 55 def record_object_changes? !@is_touch && super end