nxt_state_machine 0.1.5 → 0.1.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7e66b8a54f30382001a2c1292ac799c92335cb55835e051efb2a3d450409d67f
-  data.tar.gz: 255c9799a3732ea5ffa3b87048c5d9b6a3f185b43d1d24fb047ceefef89a9514
+  metadata.gz: 77b32ce5c0f8c968180650e6497e84076803948c832e84d5c63145ff10050c46
+  data.tar.gz: 5a5f210aaf9b8f0d8278a66851f4d3be8f278a4a448975252610b3eebe292b06
 SHA512:
-  metadata.gz: dcc9b059691980d6121fd97c2f5814bff20e717054d2c7d4b4e7e678c5b7e299906c4310ac46ebe6a11ac55b443a31248e289fd8b9858e7dbc2247341e981a83
-  data.tar.gz: 4eb4a0fdfbb88b5014c021279a89cff8638f0e01874b15da7bb45718f0de2c3050d1676ed722e6f0d537885669c43bc32c4bcfdda19319e6388325b1055dd394
+  metadata.gz: fbbf6e38dc538a6e5018d9839c591ddf707cc5d348c310582680e8cf588715545214ebe1b16ab70dddad63a0cfa97ab7d66121752ffc1034813128fdb0f2e1e7
+  data.tar.gz: ef95346d040eb48905820314241e67009d846c00c71725cc2ab24948db0e426d7cdddb1fd55c01d7e63a15d465d0342adf9d35f888d6c62d1d21ba596f19bd54

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    nxt_state_machine (0.1.5)
+    nxt_state_machine (0.1.6)
       activesupport
       nxt_registry (~> 0.1.3)
 
@@ -31,7 +31,7 @@ GEM
     pry (0.12.2)
       coderay (~> 1.1.0)
       method_source (~> 0.9.0)
-    rake (10.5.0)
+    rake (12.3.3)
     rspec (3.9.0)
       rspec-core (~> 3.9.0)
       rspec-expectations (~> 3.9.0)
@@ -61,7 +61,7 @@ DEPENDENCIES
   bundler (~> 2.0)
   nxt_state_machine!
   pry
-  rake (~> 10.0)
+  rake (~> 12.0)
   rspec (~> 3.0)
   rspec_junit_formatter
   sqlite3

data/README.md

@@ -335,8 +335,6 @@ You can raise an error, have everything rolled back and then have your error han
 error handler. You can also defuse errors. This means they will not cause a rollback of the transaction during the 
 transition and you can actually persist changes to your model before the defused error is raised and handled. 
 
-### Multiple state machines in the same class
-
 ```ruby
 state_machine do 
   # ...
@@ -344,6 +342,9 @@ state_machine do
   defuse CustomError, from: any_state, to: all_states        
  
   event :approve do
+    # You can also defuse on event level 
+    # defuse CustomError, from: %i[written submitted deleted], to: :approved 
+
     transition from: %i[written submitted deleted], to: :approved do |headline:|
       # This will be save to the database even if defused CustomError is raised after 
       article.update!(headline: headline)
@@ -353,6 +354,12 @@ state_machine do
     
   on_error! CustomError from: any_state, to: :approved do |error, transition|
     # You can still handle the defused Error if you want to 
+    # You should probably reload your model here to not accidentally save changes that 
+    # were made to the model during the transition before a non defused error was raised 
+    article.reload
+    # The error callback does not run inside the transaction. No more strings attached here. 
+    # You can now persist changes to your model again. 
+    article.update!(error: error.message)   
   end
 end
 ```
@@ -379,11 +386,7 @@ end
 
 
 ## TODO
-- Test implementations for Hash, AttrAccessor
 - Decide on how to include state methods in model classes
-- Thread safety spec!
-- Spec locks?
-- Explain locking in readme!
 - Should we clone machines for each context?
 - What about inheritance? => What would be the expected behaviour? (dup vs. no dup)
     => Might also make sense to walk the ancestors chain and collect configure blocks

data/lib/nxt_state_machine/version.rb

@@ -1,3 +1,3 @@
 module NxtStateMachine
-  VERSION = "0.1.5"
+  VERSION = "0.1.6"
 end

data/nxt_state_machine.gemspec

@@ -38,7 +38,7 @@ Gem::Specification.new do |spec|
   spec.add_dependency "nxt_registry", "~> 0.1.3"
 
   spec.add_development_dependency "bundler", "~> 2.0"
-  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rake", "~> 12.0"
   spec.add_development_dependency "rspec", "~> 3.0"
   spec.add_development_dependency "pry"
   spec.add_development_dependency "activerecord"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: nxt_state_machine
 version: !ruby/object:Gem::Version
-  version: 0.1.5
+  version: 0.1.6
 platform: ruby
 authors:
 - Andreas Robecke
@@ -11,7 +11,7 @@ authors:
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-02-14 00:00:00.000000000 Z
+date: 2020-03-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -61,14 +61,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '12.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '12.0'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement