Sha256: 304c54b3ceed9470568da10ef17c8c5ff924c748f9f55809ececcbb19749be1e
Contents?: true
Size: 1.78 KB
Versions: 4
Compression:
Stored size: 1.78 KB
Contents
# frozen_string_literal: true require "paper_trail/events/base" module PaperTrail module Events # See docs in `Base`. # # @api private class Update < Base # - 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 def initialize(record, in_after_callback, is_touch, force_changes) super(record, in_after_callback) @is_touch = is_touch @force_changes = force_changes end # Return attributes of nascent `Version` record. # # @api private def data data = { 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 # `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 https://github.com/rails/rails/issues/33429 # # @api private def record_object_changes? !@is_touch && super end end end end
Version data entries
4 entries across 4 versions & 1 rubygems