fixture_farm 1.1.2 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 205e12a455e71ef917424e9451052b3be1517b11d46f9066a5311d51e889a667
-  data.tar.gz: 360d8805f8844a6a391cf5877f13a9f2433820a6bb94c0d35ee29444ae08b415
+  metadata.gz: 92b468fd49d2062a518429bf20576066f827ff474c96bdf6fcab066ac5657824
+  data.tar.gz: '09980fce3fdb708ae0b9803a10b8c04970a9fa78dfe55cf737c2a30b6818c8a8'
 SHA512:
-  metadata.gz: 303bb7ecad05b844de71cbe3a68a814ec70a76b4adfa2eaf570752bf6de253c87c85b2a795ec69d6d0b6a7530753a73033df1d2b45366814846d401528272184
-  data.tar.gz: 6fdb88f7da8c21e4531152b7a1262b951ed0622a000cd27c61b1fc1f47ccebf5b64ca4c1cad1387e02d93612f82c71c0b73a88e7b0c6f33b2bbcf592a4d33d37
+  metadata.gz: 2982e7c153b5747d463005253c256594b7dbbf4ca8f622a44612581b7d6571834f5b28ae50d6f85c32a188c9b62f26a77f6160816cba52d5a5ab53a08e007958
+  data.tar.gz: f3f4958dcf22e728df77ead1d874a43ba603c5cfb6222bc7500848d5b06d327faad20291dbc8832e7db484e03dbf42dd90129c7fd39f1ce75d5475c397a85007

data/README.md

@@ -108,9 +108,9 @@ FixtureFarm.low_priority_parent_model_for_naming = -> { _1.is_a?(TenantModel) }
 `record_fixtures` also supports hash arguments for advanced fixture naming control:
 
 ```ruby
-# Replace 'client_1' with 'new_client' in fixture names, or use 'new_client' as prefix if not found
 record_fixtures(new_client: :client_1) do
-  User.create!(name: 'Test User', email: 'test@example.com')
+  User.create!(name: 'Test User', email: 'test@example.com', client: clients(:client_1))
+  Star.create!
 end
 ```
 
@@ -118,9 +118,9 @@ This works in two ways:
 - **Replacement**: If a generated fixture name contains `client_1`, it gets replaced with `new_client`
 - **Prefixing**: If a generated fixture name doesn't contain `client_1`, it gets prefixed with `new_client_`
 
-For example:
-- A user fixture that would be named `client_1_user_1` becomes `new_client_user_1` (replacement)
-- A user fixture that would be named `user_1` becomes `new_client_user_1` (prefixing)
+In the above example:
+- The user fixture would be named `client_1_user_1`, but the actual name will be `new_client_user_1` (replacement)
+- The star fixture would be named `star_1`, but will be named `new_client_star_1` (prefixing)
 
 ### Attachment fixtures
 

data/bin/fixture_farm.rb

@@ -4,7 +4,7 @@
 require_relative '../lib/fixture_farm/fixture_recorder'
 
 def usage
-  puts 'Usage: bundle exec fixture_farm <record|status|stop> [name_prefix|name_prefix:replaces_name]'
+  puts 'Usage: bundle exec fixture_farm <record|status|stop> [name_prefix|old_name:new_name]'
   exit 1
 end
 
@@ -12,7 +12,7 @@ case ARGV[0]
 when 'record'
   prefix_arg = ARGV[1]
 
-  # Parse hash syntax like "new_user:user_1" into {new_user: :user_1}
+  # Parse hash syntax like "user_1:new_user" into {user_1: :new_user}
   if prefix_arg&.include?(':')
     parts = prefix_arg.split(':', 2)
     parsed_prefix = { parts[0].to_sym => parts[1].to_sym }

data/lib/fixture_farm/fixture_recorder.rb

@@ -382,7 +382,7 @@ module FixtureFarm
           "#{model_instance.class.name.underscore.split('/').last}_1"
         ].select(&:present?).join('_')
 
-        @fixture_name_replacements.each do |new_name, old_name|
+        @fixture_name_replacements.each do |old_name, new_name|
           # Only apply replacement if the base_name doesn't already start with new_name
           # This prevents double-application of replacements
           next if base_name.start_with?("#{new_name}_")

data/lib/fixture_farm/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module FixtureFarm
-  VERSION = '1.1.2'
+  VERSION = '1.2.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: fixture_farm
 version: !ruby/object:Gem::Version
-  version: 1.1.2
+  version: 1.2.0
 platform: ruby
 authors:
 - artemave
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2025-08-28 00:00:00.000000000 Z
+date: 2025-09-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails