migration_data 0.0.4 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fd17cf47cfa0baf42b5c1d2352959ec3157a975b
-  data.tar.gz: de896217509a426ff6c4e937d84f761783807623
+  metadata.gz: 7d1f60bf8d7678f0a5e055ec9072236970ea0e5a
+  data.tar.gz: 0e2bfdf1e435d67eb0da4990f7b0d6169272581a
 SHA512:
-  metadata.gz: a95485cd38bf813737a1b8d2608b2fd98086b79c60f220be527228e4417580a41bc627a27a87ef07355198722ccfee9fb9876bb3be66fb1b88bc64234aff429f
-  data.tar.gz: ee4b11882e2439e0ba09baccb514ca95bad1400a7200f6865655e64788bdbc9386f1719a4091330a38648db1655722d930f1bb4478d3549ff061c5db9ee6f92e
+  metadata.gz: 7ed9ae7be493e852733dba3c5a0e71ec9f1aac4544eaa161105d97169ab7c80867e26accbc984c8382a4a5e8a358f2fdacc7e2b192633db0dd1db5488dd97a00
+  data.tar.gz: 491a28d86c4b1088e9b7dfa18c896feb00004453fda127985b2df51a7462a740a7121b7a3af332edce1bfbf7d84b3ac4a765310717717b97639963fb7d99a2b6

data/README.md

@@ -5,14 +5,14 @@
 This gem provides functionality to write any code in migrations safely without regression.
 
 Sometimes we have to write some Rails code in the migrations and it's hard to
-keep them in working state because models wich are used there changes too often. there
+keep them in a working state because models which are used there change too often. There are
 some techniques which help to avoid these pitfalls. For example, define model
-classes in the migrations or write raw SQL. But they don't help in 100% cases anyway.
-This gem promises to solve the problem in a simple way.
+classes in the migrations or write raw SQL. But they don't help in 100% of all cases.
+This gem promises to solve this problem in a simple way.
 
 Currently the gem supports Rails 4.
 
-If you still don't understand what for this gem please check out [this blob post](http://railsguides.net/2014/01/30/change-data-in-migrations-like-a-boss/).
+If you still don't understand what this gem is for please check out [this blog post](http://railsguides.net/2014/01/30/change-data-in-migrations-like-a-boss/).
 
 ## Installation
 
@@ -41,28 +41,35 @@ class CreateUsers < ActiveRecord::Migration
   def data
     User.create!(name: 'Andrey', email: 'ka8725@gmail.com')
   end
+
+  def rollback
+    User.find_by(name: 'Andrey', email: 'ka8725@gmail.com').destroy
+  end
 end
 ```
 
 That's it. Now when you run migrations with the `rake db:migrate` command the `data` method will be run on `up`.
-
-NOTE: it's not run on `down`. If you have any reason to do it please fell free to make pull request.
+When you rollback migrations with the `rake db:rollback` command the `rollback` method will be run on `down`.
 
 ## Testing migrations
 
-To keep your migrations working don't forget to write tests for them.
-Possible `RSpec` test for the migration looks like this:
+To keep your migrations working don't forget to write tests for them. It's preferably to put the tests for migrations into `spec/db/migrations` folder, but actually it's up to you. Possible `RSpec` test (`spec/db/migrations/create_user.rb`) for the migration looks like this:
 
 ```ruby
-
 require 'spec_helper'
 require 'migration_data/testing'
 require_migration 'create_users'
 
-desribe CreateUsers do
+describe CreateUsers do
   describe '#data' do
     it 'works' do
-      expect { CreateUsers.new.data }.to_not raise_exception
+      expect { described_class.new.data }.to_not raise_exception
+    end
+  end
+
+  describe '#rollback' do
+    it 'works' do
+      expect { described_class.new.rollback }.to_not raise_exception
     end
   end
 end

data/lib/migration_data/active_record/migration.rb

@@ -6,6 +6,7 @@ module MigrationData
           def exec_migration_with_data(conn, direction)
             origin_exec_migration(conn, direction)
             data if direction == :up && respond_to?(:data)
+            rollback if direction == :down && respond_to?(:rollback)
           end
 
           alias origin_exec_migration exec_migration

data/lib/migration_data/version.rb

@@ -1,3 +1,3 @@
 module MigrationData
-  VERSION = '0.0.4'
+  VERSION = '0.1.0'
 end

data/test/migration_test.rb

@@ -1,11 +1,15 @@
 require 'test_helper'
 
 class MyMigration < ActiveRecord::Migration
-  attr_reader :migrated_data
+  attr_reader :migrated_data, :rolled_back_data
 
   def data
     @migrated_data = true
   end
+
+  def rollback
+    @rolled_back_data = true
+  end
 end
 
 describe MyMigration do
@@ -23,5 +27,15 @@ describe MyMigration do
       @migration.migrate(:down)
       assert_nil @migration.migrated_data
     end
+
+    it 'runs #rollback on down direction' do
+      @migration.migrate(:down)
+      assert @migration.rolled_back_data
+    end
+
+    it "doesn't run #rollback on up direction" do
+      @migration.migrate(:up)
+      assert_nil @migration.rolled_back_data
+    end
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: migration_data
 version: !ruby/object:Gem::Version
-  version: 0.0.4
+  version: 0.1.0
 platform: ruby
 authors:
 - Andrey Koleshko
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-02-08 00:00:00.000000000 Z
+date: 2015-09-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -113,7 +113,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.0
+rubygems_version: 2.2.2
 signing_key: 
 specification_version: 4
 summary: Provides possibility to write any code in migrations safely without regression.
@@ -122,4 +122,3 @@ test_files:
 - test/migration_test.rb
 - test/require_migration_test.rb
 - test/test_helper.rb
-has_rdoc: