service_actor 3.1.0 → 3.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a514ff7ba650102221cb5062bdcba419620229af17070f8393b7dfbdbcf20eae
-  data.tar.gz: ce94d81e2a1e8cd31cf2b6087b86e71cadd7efa84b0823a420131a80477e7518
+  metadata.gz: c9d2367f70743f81df7df55ba4bc9a7fbcb5c27c08c2219abad25139763914f3
+  data.tar.gz: 107897dcd684becef83e44d9f07a2061b41a36d726120a92ebfef5ba549b4375
 SHA512:
-  metadata.gz: a0ef5dc251c17236382350ffbed06936b344dfa7276f69cc67466cb69a4bcfd408d2017d831913f12db7d72cc7b3b9743223ebd75669c23b9b04c1619480651c
-  data.tar.gz: a038729c6b37a9f6a1f29ef02fc1bc451faa4bb1eb1da62f7feef29f585c778be7cce93d62bedb81195fa6ee4fde814284778693954b8af706453730c2edc442
+  metadata.gz: 335b5893e4cc4bc8c506c0503700f2617ba845fcf9d819a70fd4e42e67116c9cd3fbf9570a4ab2660f54c00b112a49108581d1858a65bbfa3e77f97417b8336f
+  data.tar.gz: d450f69555986cf33a96fe52b5fa254e768c3c96f60e7c9dbcd345906c3c66bd4f92149e0de66d87c78059c5ecf5ba6b936705a57cbec2a773136b18bdab22ff

data/README.md

@@ -395,7 +395,7 @@ However there are a few key differences which make `actor` unique:
   and failures are not hidden away because you forgot to use `!`.
 - Allows defaults, type checking, requirements and conditions on inputs.
 - Delegates methods on the context: `foo` vs `context.foo`, `self.foo =` vs
-  `context.foo = `, fail!` vs `context.fail!`.
+  `context.foo = `, `fail!` vs `context.fail!`.
 - Shorter setup syntax: inherit from `< Actor` vs having to `include Interactor`
   and `include Interactor::Organizer`.
 - Organizers allow lambdas, being called multiple times, and having conditions.
@@ -421,9 +421,9 @@ interactive prompt.
 
 To release a new version, update the version number in `version.rb`, and in the
 `CHANGELOG.md`. Update the `README.md` if there are missing segments, make sure
-tests and linting are pristine by calling `rake`, then create a commit for this
-version. You can then run `rake release`, which will create a git tag, push
-using git, and push the gem to [rubygems.org](https://rubygems.org).
+tests and linting are pristine by calling `bundle && rake`, then create a commit
+for this version. You can then run `rake release`, which will assign a git tag,
+push using git, and push the gem to [rubygems.org](https://rubygems.org).
 
 ## Contributing
 

data/lib/service_actor/failable.rb

@@ -17,11 +17,11 @@ module ServiceActor
       def inherited(child)
         super
 
-        child.fail_ons.append(*fail_ons)
+        child.fail_ons.push(*fail_ons)
       end
 
       def fail_on(*exceptions)
-        fail_ons.append(*exceptions)
+        fail_ons.push(*exceptions)
       end
 
       def fail_ons

data/lib/service_actor/result.rb

@@ -28,7 +28,7 @@ module ServiceActor
     end
 
     def failure?
-      super || false
+      self[:failure?] || false
     end
 
     def merge!(result)

data/lib/service_actor/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module ServiceActor
-  VERSION = '3.1.0'
+  VERSION = '3.1.1'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: service_actor
 version: !ruby/object:Gem::Version
-  version: 3.1.0
+  version: 3.1.1
 platform: ruby
 authors:
 - Sunny Ripert
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-10-17 00:00:00.000000000 Z
+date: 2021-04-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -164,17 +164,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.3.7
-  - - "<"
-    - !ruby/object:Gem::Version
-      version: 2.8.0
+      version: '2.4'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.2
+rubygems_version: 3.1.6
 signing_key: 
 specification_version: 4
 summary: Service objects for your application logic