rails_async_migrations 1.0.1 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e24a2ed40f0fcdc9da52564f3cbac3164f5f51caf2b3ae4e0a0c230740c0fce3
-  data.tar.gz: 6640134d706bf44a36d3d90758cb4830837c10bfb64f008b16f8b962829275e5
+  metadata.gz: 19fc441a029878e39ee6794467b9a442d0b3b2a7a6a2190612555478ee60689a
+  data.tar.gz: bc1947d8c051d3dbdecfda22c8efabb35cc75a2a012592b8f0a67e8f67ea64ac
 SHA512:
-  metadata.gz: cf224109d383f1b7db33b8be88e6217e7fc4b771e8cd1509d2021f13619ebea6ae5aad0d4567167c7e1c1043b0d8d63b0d8261f7bee8d56a1b845f90e832447f
-  data.tar.gz: 699120d94bf4cd2aa17521efb7b034578ba81d9e8dfa02552df66ea7d19f6d60dc2ffc546da7e60f672d8a7ce0ac57b9a02c73590ec6aa86403ca2a6dac2f865
+  metadata.gz: 6300eed27ef6c4007a24757aec057f4675b2b92d3fa4606e48c9b387307065d2ae0be82c84fe404364b5a96c662542498800e75dcdfbe2f5b1ba1eb6217da563
+  data.tar.gz: 13f506f3dc6bd466da06861e22d5e0fe781510f53e5a4c4d0c03e251d0db2081c4751c7ee0f9fe36150873b5ee2ea2565091f1f7120077528899fa98559cf6d3

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    rails_async_migrations (1.0.1)
+    rails_async_migrations (1.0.2)
 
 GEM
   remote: https://rubygems.org/

data/README.md

@@ -116,9 +116,13 @@ You can also manually launch the queue check and fire by using:
 
 ## Failure handling
 
-If your migration crashes, and blocks the rest of your asynchronous migrations but you want to execute them anyway, you can change the code of the migration file and push it again so it passes, or simply remove / update as `state = done` the matching `async_schema_migrations` row.
+If your migration crashes, and blocks the rest of your queue but you want to execute them anyway, you can use multiple strategies to do so:
 
-The `version` value is always the same as the classic migrations ones.
+- Change the code of the migration file and push it again so it passes
+- Remove the matching row in the `async_schema_migrations` table
+- Update the matching row with `state = done`
+
+To find the matching migration, be aware the `version` value is always the same as the classic migrations ones, so it's pretty easy to find things around.
 
 ## Compatibility
 

data/lib/rails_async_migrations/mutators/base.rb

@@ -1,8 +1,23 @@
 module RailsAsyncMigrations
   module Mutators
     class Base
+      # in some context we have to guess it from the file and current connection
+      # for instance when we use class methods such as `turn_async`
       def migration_class
-        instance.class
+        if instance.class == ActiveRecord::Migration
+          fetch_from_file
+        else
+          instance.class
+        end
+      end
+
+      def fetch_from_file
+        require current_migration.filename
+        current_migration.name.constantize
+      end
+
+      def current_migration
+        @current_migration ||= Connection::ActiveRecord.new(:up).current_migration
       end
     end
   end

data/lib/rails_async_migrations/mutators/turn_async.rb

@@ -15,6 +15,7 @@ module RailsAsyncMigrations
       private
 
       def alter_migration
+        Tracer.new.verbose "#{migration_class} is now asynchronous"
         migration_class.include RailsAsyncMigrations::Migration
       end
     end

data/lib/rails_async_migrations/version.rb

@@ -1,3 +1,3 @@
 module RailsAsyncMigrations
-  VERSION = "1.0.1"
+  VERSION = "1.0.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rails_async_migrations
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.2
 platform: ruby
 authors:
 - Laurent Schaffner