serially 0.4.0 → 0.4.1

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    NzlmMzhlZjEwYWU1ZjRmMmUyYjA5MGVmZjZiMDQ2NTAyYzQwMzMyNQ==
+    OTg0MTE1ZGY1MDEyZGNiNWQ0MWM3OGZkNjQ1MGNiN2NiYjkxMmJhOQ==
   data.tar.gz: !binary |-
-    YjU1YjBlNGM4NjQ2ZmUxZDVkNTQyZGY2MzVkNTdlYjIyODQ4NTYwZQ==
+    ZDhhZDNmNzIxMjUwODJjZmRkODliMmUxYTZlOTEyNzI1NTlhODQ5Yg==
 SHA512:
   metadata.gz: !binary |-
-    MjFlYjZkOTcxODg5NjBiYjUzOTU0YWZmNjljZjc1NTA2OWZkYTgxNGE1ODhl
-    NmNiYTdhYzI5MzNmYzY5MGE0YmNlMDc4MmNlZjZlYTU2YmU3MTA2MzYwN2Uy
-    ODYwNDQ1YTFmOGUxMDQyMDBkNzZlYjdiYTY5N2M3OTk4NDhhNDI=
+    ODgwYWUyMDhjN2NhOWVkODYwY2UyN2YxMzJmOTBkNmJlNmE3ZmQ0MDNiODY2
+    Y2Y2ZGVjMTBkNzUxYThiNzc4MzFjNDQwZjk3NDg2ZWM4NTcyYWIwMzY5YWFm
+    OWE1YjIwM2U1OTM5NDRhNWFmNTEyYTlhMWMzNzQwZWY5NzA3MjQ=
   data.tar.gz: !binary |-
-    OGJhOTg2NDJjMzNjZDljZjY0YWRkNTE5MGE4MmEzMGVjZTM1MmUxMzNjMzA1
-    ZjljNTFhZjJhODg5ZDU5ZjQ5ZmQ4M2ZjYzRkMGI3OWFjZmFmNTcwNDIxOGU3
-    MzdiZDU4MjVlMGQ0OTdlMjRkODMxODhkYjUyOWQ5ZDliYjJiZGQ=
+    NWViNDYwZDE5ZmE4ZDY0MDc1ZTcyMTMyZjI2YWUzMjM0MjdmODZiOGYxMDhh
+    OTg1MGUyZjNkMWJjNjUwNTMwMjQ2MWFlYTJjNDkyYTZlZDFkNzE0NTJiZGM0
+    MTk5MmZiYTIxNjQ3Yjc3YTk0ZWE3YjE4M2IzZWViZTU1MjhjMTY=

data/README.md

@@ -3,10 +3,9 @@
 [![Build Status](https://circleci.com/gh/mikemarsian/serially.svg?&style=shield&circle-token=93a8f2925ebdd64032108118ef6e17eb3848d767)](https://circleci.com/gh/mikemarsian/serially)
 [![Code Climate](https://codeclimate.com/github/mikemarsian/serially/badges/gpa.svg)](https://codeclimate.com/github/mikemarsian/serially)
 
-Have you ever had a class that required a series of background tasks to run serially, strictly one after another? Then Serially is for you.
-Declare the tasks using a simple DSL in the order you want them to to run. Serially will wrap them in a single job, and schedule it using Resque
-in a queue you specify (or a default one). The next task will run only if the previous one has finished successfully. All task run results are written to DB and can be inspected (that is if
-your class is an ActiveRecord model).
+Have you ever had a class whose instances required a series of background tasks to run serially, strictly one after another? Than Serially is for you.
+Declare the tasks using a simple DSL in the order you want them to to run. The tasks for each instance will run inside a separate Resque job, in a queue you specify. The next task will run only if the previous one has finished successfully. All task runs are written to DB and can be inspected.
+
 
 Check [this demo app][1] to see how Serially may be used in a Rails app.
 
@@ -170,7 +169,7 @@ class Post < ActiveRecord::Base
      end
 end
 ```
-#### On Error Callback
+#### On Error Callbacks
 You can provide an error handling callback for each task, which will be called if a task fails to finish successfully. If the error handling
 callback returns `true`, the execution will continue to next task, despite the failure of the previous one, otherwise tasks
 execution will stop as expected.

data/lib/serially/version.rb

@@ -1,3 +1,3 @@
 module Serially
-  VERSION = "0.4.0"
+  VERSION = "0.4.1"
 end

data/serially.gemspec

@@ -36,8 +36,7 @@ Gem::Specification.new do |spec|
 
   spec.description   = <<desc
 Have you ever had a class whose instances required a series of background tasks to run serially, strictly one after another? Than Serially is for you.
-Declare the tasks using a simple DSL in the order you want them to to run. The tasks for each instance will run inside a separate Resque job, in a queue you specify. The next task will run only if the previous one has finished successfully. All task runs are written to DB and can be inspected (if
-your class is an ActiveRecord object).
+Declare the tasks using a simple DSL in the order you want them to to run. The tasks for each instance will run inside a separate Resque job, in a queue you specify. The next task will run only if the previous one has finished successfully. All task runs are written to DB and can be inspected.
 desc
 
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: serially
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.4.1
 platform: ruby
 authors:
 - Mike Polischuk
@@ -170,9 +170,7 @@ description: ! 'Have you ever had a class whose instances required a series of b
   Declare the tasks using a simple DSL in the order you want them to to run. The tasks
   for each instance will run inside a separate Resque job, in a queue you specify.
   The next task will run only if the previous one has finished successfully. All task
-  runs are written to DB and can be inspected (if
-
-  your class is an ActiveRecord object).
+  runs are written to DB and can be inspected.
 
 '
 email: