use_case 0.4.0 → 0.5.0

data/Readme.md

@@ -170,7 +170,7 @@ This is the high-level overview of how `UseCase` strings up a pipeline
 for you to plug in various kinds of business logic:
 
 ```
-User input (-> input sanitation) (-> pre-conditions) (-> builder) (-> validations) -> command
+User input (-> input sanitation) (-> pre-conditions) (-> builder) (-> validations) -> command (-> command...)
 ```
 
 * Start with a hash of user input
@@ -179,7 +179,7 @@ User input (-> input sanitation) (-> pre-conditions) (-> builder) (-> validation
 * Optionally run pre-conditions on the santized input
 * Optionally refine input by running it through a pre-execution "builder"
 * Optionally (refined) input through one or more validators
-* Execute command with (refined) input
+* Execute command(s) with (refined) input
 
 ## Input sanitation
 
@@ -221,11 +221,11 @@ dependency. To use this feature, `gem install activemodel`.
 
 When user input has passed input sanitation and pre-conditions have
 been satisfied, you can optionally pipe input through a "builder"
-before handing it over to validations and the command.
+before handing it over to validations and the commands.
 
 The builder should be an object with a `build` method. The method will
 be called with santized input. The return value from `build` will be
-passed on to validators and the command.
+passed on to validators and the commands.
 
 Builders can be useful if you want to run validations on a domain
 object rather than directly on "dumb" input.
@@ -307,7 +307,12 @@ better name is welcome.
 A command is any Ruby object that defines an `execute(params)` method. Its
 return value will be passed to the outcome's `success` block. Any errors raised
 by this method is not rescued, so be sure to wrap `use_case.execute(params)` in
-a rescue block if you're worried that it raises.
+a rescue block if you're worried that it raises. Better yet, detect known causes
+of exceptions in a pre-condition so you know that the command does not raise.
+
+A use case can execute multiple commands. When you do, the result of the first
+command will be the input to the second command and so on. The result of the
+last command will be the final `outcome.result`.
 
 ## Use cases
 

data/lib/use_case.rb

@@ -40,7 +40,8 @@ module UseCase
   end
 
   def command(command)
-    @command = command
+    @commands ||= []
+    @commands << command
   end
 
   def builder(builder)
@@ -64,7 +65,8 @@ module UseCase
       return outcome
     end
 
-    SuccessfulOutcome.new(self, @command.execute(input))
+    result = @commands.inject(input) { |input, command| command.execute(input) }
+    SuccessfulOutcome.new(self, result)
   end
 
   private

data/lib/use_case/version.rb

@@ -24,5 +24,5 @@
 #++
 
 module UseCase
-  VERSION = "0.4.0"
+  VERSION = "0.5.0"
 end

data/test/sample_use_case.rb

@@ -26,7 +26,7 @@ require "virtus"
 require "use_case"
 
 class Model
-  attr_reader :id, :name
+  attr_accessor :id, :name
 
   def initialize(id, name)
     @id = id
@@ -123,3 +123,19 @@ class CreateRepositoryWithExplodingBuilder
 
   def build; raise "Oops"; end
 end
+
+class PimpRepositoryCommand
+  def execute(repository); repository.name += " (Pimped)"; repository end
+end
+
+class CreatePimpedRepository
+  include UseCase
+
+  def initialize(user)
+    input_class(NewRepositoryInput)
+    command(CreateRepositoryCommand.new(user))
+    command(PimpRepositoryCommand.new)
+  end
+
+  def build; raise "Oops"; end
+end

data/test/use_case_test.rb

@@ -113,4 +113,11 @@ describe UseCase do
 
     assert outcome.pre_condition_failed?
   end
+
+  it "chains two commands" do
+    outcome = CreatePimpedRepository.new(@logged_in_user).execute({ :name => "Mr" })
+
+    assert_equal 1349, outcome.result.id
+    assert_equal "Mr (Pimped)", outcome.result.name
+  end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: use_case
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.5.0
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-04-03 00:00:00.000000000 Z
+date: 2013-04-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: minitest