flexibility to take ruby block.

[limjinsun]

      # @param (see Runnable#initialize)
      #
      # @return (see Runnable#run!)
      #
      # @raise (see Runnable#run!)
      def run!(*args)
        _out = new(*args).send(:run!)
        yield(_out.result) if block_given?

        _out
      end

Would you be able to change to take ruby block for flexibility?

  SomeInteraction.run!(x: 1) do |result|
    Notification.call(result)
  end

If you don't allow this, is there any reason why?

Update. with @antulik , only in run! taking block.

[antulik]

@limjinsun have you considered

SomeInteraction.run!(x: 1).then do |result|
end

Or

SomeInteraction.run!(x: 1).tap do |result|
end

Personally I see block in run is problematic as it's not clear what to do in a failed run.

[limjinsun]

Ok I agree. then what if only in run! method?
If something fail, it will throw exception, and block won't be executed.

Thanks for suggestion for that but, I am not fan of using tap. like to keep my code clean.

[antulik]

if it's only in run! then you can write

result = SomeInteraction.run!(x: 1)
Notification.call(result)

Which is cleaner in my opinion. What's the advantage of having a block?

The downside I see of only having it in run! would inconsistent interface with run.

[AaronLasseigne]

I think @antulik brings up great points. For now I think it makes sense to leave things as they are.