w_flow 0.12.0 → 0.13.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 4c6971610a0278716309118842acdfd7532ed202
-  data.tar.gz: bbda595555d7dcc881280bd7369d1456c8561ff6
+  metadata.gz: 235135c7812d63f436af147b79f205431907df25
+  data.tar.gz: a59d5c4633721eb41f8d15d20aaf23126d55db51
 SHA512:
-  metadata.gz: 2012a6ea13452f2dc30418ea861fe8f54b5dcb30723cf8aa4a372835b25a9713670695ec4efee5a187b70885f40830e15fe9ddf62c0d85d9ff8c994915c4404d
-  data.tar.gz: fca65b36b9966e01f743fe9619b9477e5200ff96ddf2b23100749d2101b6a26a15a1550cac133067c3a843a52dc9ec81e5782a120e88b3b86480055e52a1f575
+  metadata.gz: b75bee8e85673094a030890ae0cbdfc1fc84e27877a272f85425ecd7941583fbc8397b25570fdc9141deb50ce2f476226d4370d652619db8ae9215bff65af44b
+  data.tar.gz: d24a7550b75e50a392154a214b8a687bd29f6b2cf11b0b753fca8af960b49fa50840278b50771891a2d2e5ab7d70bada82f72c2405213401cf94b195ee7abd1e

data/README.md

@@ -89,7 +89,7 @@ report = SendWelcomeEmail.run(user_id: 10)
 Processes passed to execute will be called before the perform method. You can
 have as any execute as you want and as many Processes (and method nomes and Procs) in a execute.
 This means that when you run SendWelcomeEmail process, it will first execute FindUser which will
-set the user under flow.data, and than you can use that user to get the email address
+set the user under flow.data, and then you can use that user to get the email address
 for where to send the email.
 
 So far so good, but lets go back to FindUser. Looking at it, we are currently not accounting for
@@ -168,7 +168,7 @@ going on? First we try to find the user, which will raise a flow failure if no u
 is found. In this case we want to inform the admin that something went wrong, so instead of allowing
 the flow to be interrupted right away, we return false in the failure handler to cancel failure.
 After that, the second execute chain will be executed, because @no_user_found is set to true. This
-execution chain will invoke the method compose_email, SendMessageToAdmin, and than
+execution chain will invoke the method compose_email, SendMessageToAdmin, and
 call proc that reraises failure.
 
 This is some of the features of WFlow, please check [wiki](https://github.com/junhanamaki/w_flow/wiki) for more details.

data/lib/w_flow/flow.rb

@@ -1,7 +1,7 @@
 module WFlow
   class Flow
 
-    attr_reader :data
+    attr_reader :data, :failure_log
 
     def initialize(params)
       @data        = Data.new(params)

data/lib/w_flow/process.rb

@@ -63,7 +63,7 @@ module WFlow
 
         FlowReport.new(flow)
       rescue ::StandardError => e
-        raise if e.is_a?(StandardError) || !Configuration.supress_errors?
+        raise unless Configuration.supress_errors?
 
         set_failure_and_log(message: e.message, backtrace: e.backtrace)
 

data/lib/w_flow/process_worker.rb

@@ -52,8 +52,8 @@ module WFlow
     end
 
     def run
-      @process.setup
       @setup_completed = true
+      @process.setup
 
       @process_class.wflow_nodes.each do |node_class|
         node_worker = NodeWorker.new(@process, node_class)

data/lib/w_flow/version.rb

@@ -1,3 +1,3 @@
 module WFlow
-  VERSION = "0.12.0"
+  VERSION = "0.13.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: w_flow
 version: !ruby/object:Gem::Version
-  version: 0.12.0
+  version: 0.13.0
 platform: ruby
 authors:
 - junhanamaki
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2015-06-07 00:00:00.000000000 Z
+date: 2015-06-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler