fix-db-schema-conflicts 2.0.0 → 2.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 571ecba577de388058f819df72f0f3459b6afcf8
-  data.tar.gz: f0caf6caa58304c3f5fee58b8e988d53e12a9b1b
+  metadata.gz: 68adb310404b799be9a7ce31b3580e3ed4da7339
+  data.tar.gz: 45064f34cd2960f46009fedc8924fb4478ddc0a6
 SHA512:
-  metadata.gz: 5f7b58604af4db20cf2560d694af80ddf0d993bb69cbe16e5c5c712cee3d912e755dbf1ff8f47ac775896a8f923e51106232b32660c0d65b709a8e556e5babc7
-  data.tar.gz: 9ee59fa778504bf24e60998605344e7a9deab34ee6b7ac722745a162e6661a37d75188582e72fe4240198ee242b879595360111e9524aed14c69b54d0f7fc5ab
+  metadata.gz: a33b78745c8767457af0a88415b7b2192e4ef596c5af5464cfb6cf735c13971d022e6947c47008389b20fdb1783f68f3f4ab0284a00547bd9810551888173a60
+  data.tar.gz: dc8db5c6da65277c87764cff637ba9e5dc017d51f3069e4c4266bec672f45ec86c06bd4ade9bb87c8c8b0228f1cb16a855cf9307b452ff14ef58f9f825284864

data/README.md

@@ -14,11 +14,13 @@ locally, and then get a new copy of master with the other's feature and
 migration. Then when they run migrations again, John's `tasks` table looks like
 this:
 
-    t.timestamp :updated_at t.string :name
+    t.timestamp :updated_at
+    t.string :name
 
 And Sara's looks like this:
 
-    t.string :name t.timestamp :updated_at
+    t.string :name
+    t.timestamp :updated_at
 
 And every time they run migrations before committing new code, their
 `db/schema.rb` file will be showing a change, because they are flipping the
@@ -42,7 +44,9 @@ conflicts` will do the rest.
 
 Add this line to your application's Gemfile in your development group:
 
-```ruby gem 'fix-db-schema-conflicts' ```
+```ruby
+gem 'fix-db-schema-conflicts'
+```
 
 And then execute:
 
@@ -68,14 +72,17 @@ old Ruby.
 
 ## Contributors
 
- - @jakeonrails - Creator and maintainer
- - @TCampaigne
- - @Lordnibbler
- - @timdiggins
- - @zoras
- - @jensljungblad
+ - [@jakeonrails](https://github.com/jakeonrails) - Creator and maintainer
+ - [@TCampaigne](https://github.com/TCampaigne)
+ - [@Lordnibbler](https://github.com/Lordnibbler)
+ - [@timdiggins](https://github.com/timdiggins)
+ - [@zoras](https://github.com/zoras)
+ - [@jensljungblad](https://github.com/jensljungblad)
+ - [@vsubramanian](https://github.com/vsubramanian)
 
 ## Releases
+ - 2.0.1
+  - Fix bug that caused failure when project directory has a space in it
  - 2.0.0
   - Allow usage of Rubocop >= 0.38.0
   - Remove Rails 5 deprecation warnings for using alias_method_chain

data/lib/fix_db_schema_conflicts/tasks/db.rake

@@ -1,3 +1,5 @@
+require 'shellwords'
+
 namespace :db do
   namespace :schema do
     task :dump do
@@ -8,7 +10,7 @@ namespace :db do
         "#{Rails.root}/db/schema.rb"
       end
       rubocop_yml = File.expand_path('../../../../.rubocop_schema.yml', __FILE__)
-      `bundle exec rubocop --auto-correct --config #{rubocop_yml} #{filename}`
+      `bundle exec rubocop --auto-correct --config #{rubocop_yml} #{filename.shellescape}`
     end
   end
 end

data/lib/fix_db_schema_conflicts/version.rb

@@ -1,3 +1,3 @@
 module FixDBSchemaConflicts
-  VERSION='2.0.0'
+  VERSION='2.0.1'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: fix-db-schema-conflicts
 version: !ruby/object:Gem::Version
-  version: 2.0.0
+  version: 2.0.1
 platform: ruby
 authors:
 - Jake Moffatt
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-08-09 00:00:00.000000000 Z
+date: 2017-03-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler