counter_culture 0.1.26 → 0.1.27

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 46f513670a73b530008f4051a11a67e46def6f0c
-  data.tar.gz: 3f004c832368bcff24aa5f1fd6b0121d89d38fe6
+  metadata.gz: 0a6617f402a2f12b17289ebbc288430b8c4131b2
+  data.tar.gz: c8deddb0f6d99f335f6d898c80b6155122b492d3
 SHA512:
-  metadata.gz: 149514535d47feb3fac3d3ea389945c7bd66dd2c578e321b35cb3bd33b242b3130fb3c9824dfd665a0b21c6611327f23d7244f3d841cf3b05ac6d9a428704922
-  data.tar.gz: c4621358a00d034452b0b56f43e56664480c7a6b7058bbf956cda52409a9789ce8803da216001e70cb07ff1250ad2044b8477ba787756e709784e348dea8b4d0
+  metadata.gz: 7f850d6a52092714787e92a01a161c3ddcde4610cd6fe2bd9fdddeb52db180f2f32bed5804b7842e0287614aadbab94cfa2ee06c4bc45ad0329fcf2f78e42eed
+  data.tar.gz: 892d46d65415814bb4b395499ccaa27a74306a7dfc03a8f601da813a99d59eb8702da3c89a46c823981c4244f093d8f2bd393c2b967b28e0b65d84a40a1f5104

data/Gemfile

@@ -9,7 +9,6 @@ group :development, :test do
   gem "rake"
   gem "rails", '>= 3.1.0'
   gem "rspec", "~> 2.10.0"
-  gem "after_commit_action"
   gem "awesome_print"
 end
 

data/Gemfile.lock

@@ -28,8 +28,6 @@ GEM
       thread_safe (~> 0.1)
       tzinfo (~> 1.1)
     addressable (2.3.6)
-    after_commit_action (0.1.3)
-      activerecord (>= 3.0.0)
     arel (5.0.1.20140414130214)
     awesome_print (1.2.0)
     builder (3.2.2)
@@ -130,7 +128,6 @@ PLATFORMS
   ruby
 
 DEPENDENCIES
-  after_commit_action
   awesome_print
   bundler (>= 1.2.0)
   database_cleaner (>= 1.1.1)

data/README.md

@@ -243,7 +243,7 @@ counter_culture currently does *not* support polymorphic associations. Check [th
 
 counter_culture will not update counters in your automated tests *if* you use transactional fixtures. That's because transactional fixtures roll back all your database transactions and they are never committed. But counter_culture will only update its counters in the ```after_commit``` callback, which in this case will never run.
 
-counter_culture itself has extensive automated tests so there should not be a need to test counter caches in your own tests. I therefore recommend removing any checks of counter caches as that will avoid this issue. If that is not an option for you, you will have to turn off transactional fixtures and use something like [database_cleaner](https://github.com/bmabey/database_cleaner) instead to clean your database between tests.
+counter_culture itself has extensive automated tests so there should not be a need to test counter caches in your own tests. I therefore recommend removing any checks of counter caches as that will avoid this issue. If that is not an option for you, you can use the [`test_after_commit` gem](https://github.com/grosser/test_after_commit) to trigger `after_commit` callbacks even with transactional fitures enabled. Another option is to turn off transactional fixtures and use something like [database_cleaner](https://github.com/bmabey/database_cleaner) instead to clean your database between tests.
 
 ## Contributing to counter_culture
  

data/Rakefile

@@ -21,6 +21,8 @@ Jeweler::Tasks.new do |gem|
   gem.description = %Q{counter_culture provides turbo-charged counter caches that are kept up-to-date not just on create and destroy, that support multiple levels of indirection through relationships, allow dynamic column names and that avoid deadlocks by updating in the after_commit callback.}
   gem.email = "magnus@vonkoeller.de"
   gem.authors = ["Magnus von Koeller"]
+
+  gem.add_dependency 'after_commit_action', '~> 0.1.3' 
 end
 Jeweler::RubygemsDotOrgTasks.new
 

data/VERSION

@@ -1 +1 @@
-0.1.26
+0.1.27

data/counter_culture.gemspec

@@ -2,11 +2,11 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: counter_culture 0.1.26 ruby lib
+# stub: counter_culture 0.1.27 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "counter_culture"
-  s.version = "0.1.26"
+  s.version = "0.1.27"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib"]
@@ -116,30 +116,30 @@ Gem::Specification.new do |s|
       s.add_development_dependency(%q<rake>, [">= 0"])
       s.add_development_dependency(%q<rails>, [">= 3.1.0"])
       s.add_development_dependency(%q<rspec>, ["~> 2.10.0"])
-      s.add_development_dependency(%q<after_commit_action>, [">= 0"])
       s.add_development_dependency(%q<awesome_print>, [">= 0"])
       s.add_development_dependency(%q<rdoc>, ["~> 3.12"])
       s.add_development_dependency(%q<bundler>, [">= 1.2.0"])
       s.add_development_dependency(%q<jeweler>, ["~> 2.0.1"])
+      s.add_runtime_dependency(%q<after_commit_action>, ["~> 0.1.3"])
     else
       s.add_dependency(%q<rake>, [">= 0"])
       s.add_dependency(%q<rails>, [">= 3.1.0"])
       s.add_dependency(%q<rspec>, ["~> 2.10.0"])
-      s.add_dependency(%q<after_commit_action>, [">= 0"])
       s.add_dependency(%q<awesome_print>, [">= 0"])
       s.add_dependency(%q<rdoc>, ["~> 3.12"])
       s.add_dependency(%q<bundler>, [">= 1.2.0"])
       s.add_dependency(%q<jeweler>, ["~> 2.0.1"])
+      s.add_dependency(%q<after_commit_action>, ["~> 0.1.3"])
     end
   else
     s.add_dependency(%q<rake>, [">= 0"])
     s.add_dependency(%q<rails>, [">= 3.1.0"])
     s.add_dependency(%q<rspec>, ["~> 2.10.0"])
-    s.add_dependency(%q<after_commit_action>, [">= 0"])
     s.add_dependency(%q<awesome_print>, [">= 0"])
     s.add_dependency(%q<rdoc>, ["~> 3.12"])
     s.add_dependency(%q<bundler>, [">= 1.2.0"])
     s.add_dependency(%q<jeweler>, ["~> 2.0.1"])
+    s.add_dependency(%q<after_commit_action>, ["~> 0.1.3"])
   end
 end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: counter_culture
 version: !ruby/object:Gem::Version
-  version: 0.1.26
+  version: 0.1.27
 platform: ruby
 authors:
 - Magnus von Koeller
@@ -52,20 +52,6 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 2.10.0
-- !ruby/object:Gem::Dependency
-  name: after_commit_action
-  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: awesome_print
   requirement: !ruby/object:Gem::Requirement
@@ -122,6 +108,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 2.0.1
+- !ruby/object:Gem::Dependency
+  name: after_commit_action
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.1.3
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.1.3
 description: counter_culture provides turbo-charged counter caches that are kept up-to-date
   not just on create and destroy, that support multiple levels of indirection through
   relationships, allow dynamic column names and that avoid deadlocks by updating in