migration_data 0.3.0 → 0.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 7c8dbb5b25cfbd8b8e4c6b83e81fb23481644a48
-  data.tar.gz: 92f5bc8d4c74dbdc460430553a76ff2cc7015507
+  metadata.gz: 2241ab7f5357ed22a693a1757bd85b8b070d2f9c
+  data.tar.gz: 7243033a82ab6b8d84be2b785c7a4746d800ac4a
 SHA512:
-  metadata.gz: 3f4d04e8978a30b390c11371b3657ac806df432fc24831b830450975b49e09098f321051cf2d6b0913f931ec10599fe0f6089f5fa41f8ef502a379056ae868d7
-  data.tar.gz: d4d7a9e33cc75794e073da3b2a3c9ea7980bd6496cd090b726f284d37ac891acd87f8bf8b8a92e5670ee2a9f85f37e91b728f220824150671bc3be534f821647
+  metadata.gz: 8ee640f1feda47ff6e8a1cc4ce594a45515d7d4450b65919309c071f4ebb86d384da5236534aa5f6d33c92ecc0cb2e3d534e73f8859ed2b709910fd2cde45088
+  data.tar.gz: 25316582cbbcd0bd4d7a20a94441a7e88205f51bea014c6b69b5e99ea6514172f76d10c8d0fd8de5a7533dff833ec4b3077e2e97a8b15323dc1c3a8e17a667b5

data/.travis.yml

@@ -2,6 +2,6 @@ language: ruby
 before_install:
   - gem install bundler -v 1.11.2
 rvm:
-  - 2.1.0
   - 2.2.2
   - 2.3.0
+  - 2.4.0

data/README.md

@@ -10,7 +10,7 @@ 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% of all cases.
 This gem promises to solve this problem in a simple way.
 
-Currently the gem supports Rails 4.
+Currently the gem supports Rails 4 and Rails 5.
 
 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/).
 
@@ -51,6 +51,8 @@ end
 That's it. Now when you run migrations with the `rake db:migrate` command the `data` method will be run on `up`.
 When you rollback migrations with the `rake db:rollback` command the `rollback` method will be run on `down`.
 
+> Note: in some circumstances, the `reset_column_information` method should be called on a model which table is changed in the migration. Especially when you are certain that there should be present some column for a model but it's absent for some reason. Read more about this in the [official Rails docs](http://guides.rubyonrails.org/v4.1/migrations.html#using-models-in-your-migrations).
+
 ## Testing migrations
 
 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:

data/lib/migration_data/testing.rb

@@ -2,10 +2,10 @@ require 'rails'
 
 def require_migration(migration_name)
   path = MigrationData::ActiveRecord::Migration.migration_dir
-  all_migrations = ActiveRecord::Migrator.migrations(path)
+  migrations = all_migrations(path)
 
   migration_name += '.rb' unless migration_name.end_with?('.rb')
-  file = all_migrations.detect do |m|
+  file = migrations.detect do |m|
     m.filename.end_with?(migration_name)
   end
 
@@ -13,3 +13,11 @@ def require_migration(migration_name)
 
   require Rails.root.join(file.filename)
 end
+
+def all_migrations(path)
+  if Rails::VERSION::MAJOR >= 5 && Rails::VERSION::MINOR >= 2
+    ActiveRecord::MigrationContext.new(path).migrations
+  else
+    ActiveRecord::Migrator.migrations(path)
+  end
+end

data/lib/migration_data/version.rb

@@ -1,3 +1,3 @@
 module MigrationData
-  VERSION = '0.3.0'
+  VERSION = '0.3.1'
 end

data/test/migration_test.rb

@@ -1,6 +1,6 @@
 require 'test_helper'
 
-class MyMigration < ActiveRecord::Migration
+class MyMigration < ActiveRecord::Migration[4.2]
   attr_reader :migrated_data, :rolled_back_data
 
   def data

data/test/support/create_table_migration.rb

@@ -1,4 +1,4 @@
-class CreateTableMigration < ActiveRecord::Migration
+class CreateTableMigration < ActiveRecord::Migration[4.2]
   def change
     create_table :users, force: true do |t|
       t.string :name

metadata

@@ -1,55 +1,55 @@
 --- !ruby/object:Gem::Specification
 name: migration_data
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.3.1
 platform: ruby
 authors:
 - Andrey Koleshko
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-12-09 00:00:00.000000000 Z
+date: 2018-10-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '1.5'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '1.5'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: sqlite3
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 description: |-
@@ -64,8 +64,8 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
-- .travis.yml
+- ".gitignore"
+- ".travis.yml"
 - Gemfile
 - LICENSE.txt
 - README.md
@@ -100,17 +100,17 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.14.1
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: Provides possibility to write any code in migrations safely without regression.