UseCases pattern spike - part 1 - just for fun!

use_cases-transactions_use_cases.rb

# 1. So, we are all factoring out of our controllers into Query
# Objects, Command Objects and Service Objects, to name a few, 
# right?
#
# But all of that knowledge about which commands to call and what
# objects to create still ends up as an additional responsibility
# burden on the controller class.
#
# What if we wanted something that was as simple as registering the
# commands for a set of controller use cases, with either a command
# class to be called, or a method defined in the UseCase class?
#
# Something like this:

module UseCases
  class TransactionsUseCases < UseCases::Base

    register_command 'CreateNewTransaction', on: :create
    register_command :find_transaction, on: :show

    def find_transaction
      transaction = Queries::TransactionQuery.new.find_by(id: command_args[:id])
      transaction ? success(transaction) : failure
    end

  end
end

# part 2: https://gist.github.com/RichardJordan/39f32d18495276cbee1bf36b7eb28db2