active_record_merger 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 82e89e6af09708612c603982a047916c65f9dd6922bcbec285d4b94f70d6b980
+  data.tar.gz: 1df6c7c113de356ad06943f281d1da1d6c45c36a91ff9e00aad345a0275dcc44
+SHA512:
+  metadata.gz: 79207c42bef32d660bbf423e6d383884e9915e2da9303d790c7684702bd3a053b3cadf34beb51620ad6f2c7474c2fc19af7c03a223e55067d600554c02f1852c
+  data.tar.gz: 5f31936fb1c469aae52613b7d647f57ceb3fe06466da1549cd28e6ee251d2a35bb951f0c69f65363ba5efa4c2b77e442dfae21cda399541af7885b861ca90eb2

data/.idea/workspace.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="PropertiesComponent">{
+  &quot;keyToString&quot;: {
+    &quot;settings.editor.selected.configurable&quot;: &quot;settings.sync&quot;
+  }
+}</component>
+</project>

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at max@buslaev.net. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Gemfile

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in active_record_merger.gemspec
+gemspec
+
+gem "rake", "~> 13.0"
+
+gem "rspec", "~> 3.0"

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2024 Max Buslaev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,222 @@
+# ActiveRecordMerger
+
+The `ActiveRecordMerger` gem provides functionality for merging ActiveRecord objects along with their associated records. It's designed to simplify the process of combining duplicate records into a single record, while also ensuring that all associated data is correctly updated and maintained.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'active_record_merger'
+```
+
+And then execute:
+
+```bash
+bundle install
+```
+
+Or install it yourself as:
+
+```bash
+gem install active_record_merger
+```
+
+## Usage
+
+`ActiveRecordMerger` is designed to assist in merging two ActiveRecord objects and their associated records. This can be especially useful for consolidating duplicate records in your database.
+
+### Basic Setup
+
+Before you begin, you must decide which of the two records will be the 'primary' record (the one to be kept) and which will be the 'secondary' record (the one to be merged and then optionally deleted). By default, without any custom logic, `ActiveRecordMerger` will not alter the attributes of the primary record.
+
+```ruby
+primary_record = YourModel.find(primary_id)
+secondary_record = YourModel.find(secondary_id)
+
+merger = ActiveRecordMerger::RecordMerger.new(
+  primary_record,
+  secondary_record,
+  options: {} # Additional options can be provided here
+)
+merge_result = merger.call
+```
+
+In this basic example, `merge_result` will contain information about the merge process, such as which associations were updated. Note that without additional configurations, no attributes from the secondary record will be copied to the primary record, and no records will be destroyed.
+
+
+## Default Options and Customization
+
+The `ActiveRecordMerger` provides several options to customize the merging process. By default, these options are set to perform the most common actions expected during a record merge, but they can be customized to fit specific needs:
+
+1. **primary_record_resolver**: Determines which of the two records is considered the 'primary' record. By default, this is `nil`, meaning the first record provided to the merger is treated as the primary record.
+
+2. **merge_logic**: Defines how attributes from the secondary record should be merged into the primary record. The default is `nil`, indicating that no attribute merging occurs unless explicitly specified.
+
+3. **update_logic**: Provides custom logic for updating associations to re-associate the secondary record's related objects to the primary record. The default is `nil`, which updates foreign keys on direct associations (has_many, has_one) from the secondary to the primary record without additional logic.
+
+4. **destroy_merged_record**: Controls whether the secondary record should be destroyed after the merging process. The default is `false`, meaning the secondary record will remain in the database unless this option is explicitly set to `true`.
+
+5. **filter**: A callable object (like a lambda or Proc) that filters which associations should be updated based on certain criteria. By default, this is `->(assoc) { :belongs_to != assoc.type && assoc.through.nil? && !assoc.polymorphic }`, meaning we filter out all associations that are not direct or that are `:belongs_to`.
+
+### Using Filters
+
+Filters allow you to specify which associations should be updated when merging records. This can be particularly useful if you only want to update certain types of associations or if you want to exclude specific associations based on certain conditions.
+
+For example, if you only want to update `has_many` and `has_one` associations, and ignore `belongs_to` and `has_and_belongs_to_many` associations, you can use the following filter:
+
+```ruby
+options = {
+  filter: ->(assoc) {
+    [:has_many, :has_one].include?(assoc.type) && !assoc.polymorphic
+  }
+}
+```
+
+In this example, the filter is a lambda that checks the type of each association. It returns `true` only for associations that are either `has_many` or `has_one` and not polymorphic, meaning only these associations will be considered for updating during the merge process.
+
+You can customize this filter further to include your business logic, for example, excluding certain associations based on their name or custom options:
+
+```ruby
+options = {
+  filter: ->(assoc) {
+    # Only update associations that are not polymorphic and are not named :account
+    !assoc.polymorphic && assoc.name != :account
+  }
+}
+```
+
+In this adjusted example, the filter additionally prevents any association named `:account` from being updated, regardless of its type.
+
+
+### Customizing Merge Behavior
+
+You can customize the merge behavior by providing lambdas (or any other callable object) for various operations:
+
+1. **Primary Record Resolver (`:primary_record_resolver`):**
+
+   Determines which record should be considered primary. By default, the first record provided is treated as primary.
+
+    ```ruby
+    options = {
+      primary_record_resolver: lambda { |first, second| [first, second].min_by(&:created_at) }
+    }
+    ```
+
+   This example chooses the older record as the primary record.
+
+2. **Merge Logic (`:merge_logic`):**
+
+   Defines how to merge attributes from the secondary record into the primary record. By default, attributes are not merged.
+
+    ```ruby
+    options = {
+      merge_logic: lambda { |primary, secondary| 
+        primary.update(name: secondary.name) if primary.name.blank?
+      }
+    }
+    ```
+
+   In this example, the primary record’s name is updated with the secondary's name if it was originally blank.
+
+3. **Update Logic (`:update_logic`):**
+
+   Custom logic for how associated records should be updated. This is important for re-associating related records from the secondary record to the primary record.
+
+    ```ruby
+    options = {
+      update_logic: lambda { |association, primary, secondary|
+        # Custom association update logic here
+      }
+    }
+    ```
+
+   Define how each association should handle transferring related records from the secondary to the primary record.
+
+4. **Destroy Merged Record (`:destroy_merged_record`):**
+
+   Determines whether the secondary record should be destroyed after merging.
+
+    ```ruby
+    options = {
+      destroy_merged_record: true
+    }
+    ```
+
+   If set to `true`, the secondary record will be deleted from the database after the merge process is complete.
+
+### Comprehensive Example
+
+Combining all the options for a full-fledged merge process:
+
+```ruby
+options = {
+  primary_record_resolver: lambda { |first, second| [first, second].min_by(&:created_at) },
+  merge_logic: lambda { |primary, secondary| 
+    primary.update(name: secondary.name) if primary.name.blank?
+  },
+  update_logic: lambda { |association, primary, secondary| 
+    # Update association references from secondary to primary
+  },
+  destroy_merged_record: true
+}
+
+merger = ActiveRecordMerger::RecordMerger.call(primary_record, secondary_record, options)
+merge_result = merger.result
+```
+
+This comprehensive example sets up a merger that chooses the oldest record as the primary, updates the primary record's name if it was blank, re-associates related records, and then deletes the secondary record after the merge.
+
+
+
+## Return Values and Error Handling
+
+The `ActiveRecordMerger` utilizes `SimpleCommand` for executing the merge process, providing structured outcomes and error handling.
+
+### Result of Merge Operation
+
+After the merge operation is completed using the `.call` method, the result can be accessed via the `@result` instance variable of the `RecordMerger` object. This result contains information about the merge process, typically including updated records count or other relevant data depending on the provided options and the merge logic:
+
+```ruby
+merger = ActiveRecordMerger::RecordMerger.call(primary_record, secondary_record, options)
+
+if merger.success?
+  puts "Merge successful!"
+  merge_details = merger.result
+  # Access detailed result information from merge_details
+else
+  puts "Merge failed: #{merger.errors.full_messages.join(', ')}"
+end
+```
+
+In this example, `merger.result` will contain the outcome of the merge operation if it was successful. The exact structure of this result depends on how you've implemented your merge logic and what information you've chosen to include.
+
+### Handling Errors
+
+If there are any issues during the merge process, such as validation failures or conflicts in the custom logic, the errors will be accumulated in the `.errors` method of the `RecordMerger` object. This method returns an instance of `SimpleCommand::Errors`, which provides a list of error messages:
+
+```ruby
+unless merger.success?
+  puts "Merge failed due to the following errors:"
+  merger.errors.full_messages.each { |error_message| puts "- #{error_message}" }
+end
+```
+
+These errors can be used to understand what went wrong during the merge process and to inform users of the specific issues that need resolution. The `success?` method, provided by `SimpleCommand`, is a convenient way to check whether the operation completed successfully or if there were errors that prevented a successful merge.
+
+
+## Configuration
+
+No additional configuration is required. However, you can customize the behavior by providing different options as shown above.
+
+## Contributing
+
+Contributions are welcome! Feel free to open a pull request or an issue to propose changes or additions.
+
+## License
+
+The gem is available as open source under the terms of the MIT License.
+
+## Code of Conduct
+
+Everyone interacting in the ActiveRecordMerger project's codebase, issue trackers, chat rooms, and mailing lists is expected to follow the code of conduct.

data/Rakefile

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: :spec

data/active_record_merger.gemspec

@@ -0,0 +1,38 @@
+# frozen_string_literal: true
+
+require_relative "lib/active_record_merger/version"
+
+Gem::Specification.new do |spec|
+  spec.name    = "active_record_merger"
+  spec.version = ActiveRecordMerger::VERSION
+  spec.authors = ["Max Buslaev"]
+  spec.email   = ["max@buslaev.net"]
+
+  spec.summary               = "A utility gem for merging ActiveRecord objects and their associated records with customizable logic."
+  spec.description           = "ActiveRecordMerger provides an extendable framework for merging ActiveRecord models, including complex scenarios involving associations, while ensuring data integrity and providing hooks for custom merge logic."
+  spec.homepage              = "https://github.com/austerlitz/active_record_merger"
+  spec.license               = "MIT"
+  spec.required_ruby_version = ">= 2.6.0"
+
+  spec.metadata["homepage_uri"]    = spec.homepage
+  spec.metadata["source_code_uri"] = "https://github.com/yourusername/active_record_merger"
+  spec.metadata["changelog_uri"]   = "https://github.com/yourusername/active_record_merger/blob/main/CHANGELOG.md"
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files         = Dir.chdir(__dir__) do
+    `git ls-files -z`.split("\x0").reject do |f|
+      (File.expand_path(f) == __FILE__) || f.start_with?(*%w[bin/ test/ spec/ features/ .git .circleci appveyor])
+    end
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+
+  spec.add_dependency "activerecord", ">= 5.0"
+  spec.add_dependency "simple_command"
+
+  spec.add_development_dependency "rspec", "~> 3.10"
+  spec.add_development_dependency "pry", "~> 0.13.0"
+end

data/lib/active_record_merger/association_finder.rb

@@ -0,0 +1,27 @@
+# frozen_string_literal: true
+
+module ActiveRecordMerger
+  module AssociationFinder
+    extend self
+
+    AssociationInfo = Struct.new(:name, :type, :class_name, :foreign_key, :through, :polymorphic,
+                                 :foreign_type, keyword_init: true)
+
+    # Finds and returns associations for a given ActiveRecord model.
+    def call(model_class, filter = ->(_assoc) { true })
+      model_class.reflect_on_all_associations.map do |assoc|
+        AssociationInfo.new(
+          name:         assoc.name,
+          type:         assoc.macro,
+          class_name:   assoc.class_name,
+          foreign_key:  assoc.foreign_key,
+          foreign_type: assoc.foreign_type,
+          through:      assoc.options[:through],
+          polymorphic:  assoc.options[:polymorphic],
+        )
+      end.select { |assoc| filter.call(assoc) }
+    end
+
+  end
+end
+

data/lib/active_record_merger/record_merger.rb

@@ -0,0 +1,113 @@
+# frozen_string_literal: true
+require 'simple_command'
+require 'active_record'
+require_relative 'association_finder'
+
+module ActiveRecordMerger
+  ##
+  # This class performs the merging of two ActiveRecord objects of the same type.
+  # It updates associated records to reflect the merge and can optionally destroy the merged record.
+  #
+  class RecordMerger
+    prepend ::SimpleCommand
+
+    attr_reader :primary_record, :secondary_record, :update_counts, :options
+
+    ##
+    # Initializes the RecordMerger service object.
+    # @param first [ActiveRecord::Base] The record to merge into.
+    # @param second [ActiveRecord::Base] The record to merge from.
+    # @param options [Hash] The options to customize the merge process.
+    # @option options [Proc] :primary_record_resolver (nil) A lambda or Proc that determines which record is considered primary.
+    # @option options [Proc] :merge_logic (nil) A lambda or Proc that defines how to merge data from the secondary record into the primary record.
+    # @option options [Boolean] :destroy_merged_record (false) Whether to destroy the merged (secondary) record after the merge.
+    # @option options [Proc] :filter (->(assoc) { true }) A lambda or Proc that filters which associations should be updated.
+    # @option options [Proc] :update_logic (nil) A lambda or Proc that provides custom logic for updating associations.
+    #
+    def initialize(first, second, **options)
+      @_first        = first
+      @_second       = second
+      @options       = default_options.merge(options)
+      @update_counts = {}
+    end
+
+    ##
+    # Executes the merge operation.
+    # Returns a hash containing the counts of updated records for each association, and the destruction status of the merged record.
+    # @return [Hash] The result of merge operation with update counts and destruction status.
+    #
+    def call
+      ::ActiveRecord::Base.transaction do
+        ensure_same_class
+        resolve_primary_and_secondary
+        apply_merge_logic
+        update_associations
+        destroy_secondary_record if options[:destroy_merged_record]
+      end
+      @update_counts
+    rescue => e
+      errors.add(:base, "Failed to merge records: #{e.message}")
+      nil
+    end
+
+    private
+
+    # Provides default options for merging records.
+    # @return [Hash] Default options for merge.
+    def default_options
+      {
+        filter:                  ->(assoc) {
+          :belongs_to != assoc.type && assoc.through.nil? && !assoc.polymorphic
+        },
+
+        destroy_merged_record:   false,
+        primary_record_resolver: nil,
+        merge_logic:             nil,
+        update_logic:            nil,
+      }
+    end
+
+    def ensure_same_class
+      unless @_first.class == @_second.class
+        raise ::ArgumentError, 'Records must be of the same class to be merged.'
+      end
+    end
+
+    # Resolves which record should be considered the primary and which the secondary.
+    def resolve_primary_and_secondary
+      # Determine the primary record using the custom logic provided by the resolver.
+      @primary_record = options[:primary_record_resolver] ? options[:primary_record_resolver].call(@_first, @_second) : @_first
+
+      # The secondary record is the one that is not the primary.
+      @secondary_record = @_first == @primary_record ? @_second : @_first
+    end
+
+    # Applies custom logic for merging data from the secondary record into the primary record.
+    def apply_merge_logic
+      options[:merge_logic]&.call(@primary_record, @secondary_record)
+    end
+
+    # Updates associations from the secondary record to reference the primary record.
+    def update_associations
+      associations = AssociationFinder.call(@primary_record.class, options[:filter])
+      associations.each do |assoc|
+        if options[:update_logic]
+          # Here, we're passing the association, the primary record, and the secondary record to the custom logic
+          @update_counts[assoc.name] = options[:update_logic].call(assoc, @primary_record, @secondary_record)
+        else
+          # Default update logic: re-associate records from the secondary to the primary
+          associated_class           = assoc.class_name.constantize
+          foreign_key                = assoc.foreign_key
+          @update_counts[assoc.name] = associated_class.where(foreign_key => @secondary_record.id).update_all(foreign_key => @primary_record.id)
+        end
+      end
+    end
+
+    # Destroys the secondary record if flagged for destruction.
+    def destroy_secondary_record
+      @secondary_record.destroy
+      @update_counts[:destroyed] = @secondary_record.destroyed?
+    end
+
+  end
+end

data/lib/active_record_merger/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module ActiveRecordMerger
+  VERSION = "0.1.0"
+end

data/lib/active_record_merger.rb

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require_relative "active_record_merger/version"
+require_relative "active_record_merger/association_finder"
+require_relative "active_record_merger/record_merger"
+
+module ActiveRecordMerger
+  class Error < StandardError; end
+  # Your code goes here...
+end

data/sig/active_record_merger.rbs

@@ -0,0 +1,4 @@
+module ActiveRecordMerger
+  VERSION: String
+  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+end

metadata

@@ -0,0 +1,118 @@
+--- !ruby/object:Gem::Specification
+name: active_record_merger
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Max Buslaev
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2024-03-24 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: activerecord
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '5.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '5.0'
+- !ruby/object:Gem::Dependency
+  name: simple_command
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.10'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.10'
+- !ruby/object:Gem::Dependency
+  name: pry
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.13.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.13.0
+description: ActiveRecordMerger provides an extendable framework for merging ActiveRecord
+  models, including complex scenarios involving associations, while ensuring data
+  integrity and providing hooks for custom merge logic.
+email:
+- max@buslaev.net
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".idea/workspace.xml"
+- ".rspec"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- active_record_merger.gemspec
+- lib/active_record_merger.rb
+- lib/active_record_merger/association_finder.rb
+- lib/active_record_merger/record_merger.rb
+- lib/active_record_merger/version.rb
+- sig/active_record_merger.rbs
+homepage: https://github.com/austerlitz/active_record_merger
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/austerlitz/active_record_merger
+  source_code_uri: https://github.com/yourusername/active_record_merger
+  changelog_uri: https://github.com/yourusername/active_record_merger/blob/main/CHANGELOG.md
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.6.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.2.3
+signing_key: 
+specification_version: 4
+summary: A utility gem for merging ActiveRecord objects and their associated records
+  with customizable logic.
+test_files: []