Kase

NOTE: This repo is no longer maintained.

Kase gracefully pattern matches [:ok, result]-like return values.

It is a tool to avoid using exceptions as flow control and to write safer and more readable code.

The idea is inspired by Elixir in which many functions returns something like {:ok, result} or {:error, :not_found, "More specific error message"}.

In Ruby we would usually handle those kind of return values like this:

status, result, message = complete_order(cart)

case status
when :ok
  order = result
  process_order(order)
when :error
  error_kind = result
  case error_kind
  when :not_found
    [404, {}, "Not found"]
  when :invalid_state
    [400, {}, "Invalid request: #{message}"]
  else
    raise "Unhandled error kind: #{error_kind}"
  end
else
  raise "Unhandles status: #{status}"
end

This is hard to read.

Furthermore, the two lines that raises exception on unhandled status and error_kind are probably getting zero code coverage (otherwise we would have handled that specific status or error_kind).

With Kase we can do this instead, which is equivalent to the above:

kase complete_order(cart) do
  on :ok do |order|
    process_order(order)
  end

  on :error, :not_found do
    [404, {}, "Not found"]
  end

  on :error, :invalid_state do |message|
    [400, {}, "Invalid request: #{message}"]
  end
end

This is much more easy to read and reason about.

See below for a full list of what Kase does.

Add this line to your application's Gemfile:

gem "kase", "~> 0.1"

kase is the method used to match an array of values (typically a [status, result]-like array) against a number of "patterns" using the on-method. A pattern in this sense is just some values matching the array from the beginning using ==.

E.g. the pattern :a, :b matches [:a, :b] and [:a, :b, :c], but not [:c, :a, :b].

The block in the first pattern that matches will be executed, and the return value from that block is the return value of kase.

If no patterns match, a Kase::NoMatchError is raised.

An empty pattern will match everything, so that can be used as a catch-all.

The values yielded to the block are all the values that is not part of the pattern. E.g. if [:ok, "THE RESULT"] is matched with on(:ok, &block), "THE RESULT" is yielded to block.

require "kase"

Kase.kase process_order do
  on :ok do
    puts "Great success!"
  end

  on :error do
    puts "BOOM"
  end
end

This will output "Great success" if process_order returns :ok, [:ok] or [:ok, some, more, values, here].

It will output "BOOM" if process_order returns :error, [:error] or [:error, some, more, values]

If process_order returns something that is not matched, e.g. :not_found, this will raise a Kase::NoMatchError.

In the above example we don't use the values returned by process_order, if more than one value is returned.

All values that are not part of the pattern will be yielded to the given block:

require "kase"

Kase.kase process_order do
  on :ok do |order|
    puts "Great success: #{order.inspect}"
  end

  on :error do |reason, message|
    puts "BOOM! #{reason}: #{message}"
  end
end

Notice that we don't have to return the same number of values for each case to be able to catch and use the values.

We can match on multiple values, but only from the left:

require "kase"

kase process_order do
  on :ok do |order|
    puts "Great success: #{order.inspect}"
  end

  on :error, :not_found do
    puts "Not found!"
  end

  on :error, :invalid_record do |message|
    puts "Invalid record: #{message}"
  end
end

This kase will handle [:ok, order], [:error, :not_found] and [:error, :invalid_record, "Message"], but will raise a Kase::NoMatchError on e.g. [:error, :not_authorized]

Sometimes we only expect the :ok status to appear. In that case we can use ok! as a shorthand.

It can rewrite this:

kase something do
  on :ok do |result|
    handle_result(result)
  end
end

To this:

ok! something do |result|
  handle_result(result)
end

Or this:

result = kase something do
  on(:ok) { |result| result }
end

To this:

result = ok! something

Kase is a module with helper methods. You can either include it in your own class or use the methods as module functions. So both of these will work:

require "kase"

class MyFirstClass
  include Kase

  def call
    kase some_result do
      ...
    end
  end
end

class MySecondClass
  def call
    Kase.kase some_result do
      ...
    end
  end
end

Note that #kase is aliased to #call so you can use the shorthand Kase.(values).

All the logic resides in the Kase::Switcher class which you can use directly if you need to:

switcher = Kase::Switcher.new(:ok, "RESULT")
switcher.on(:ok) { |result| puts result }
switcher.on(:error) { |message| warn message }
switcher.validate!
result = switcher.result

The above is equivalent to:

result = Kase.kase :ok, "RESULT" do
  on(:ok) { |result| puts result }
  on(:error) { |message| warn message }
end

• Install development dependencies with bundle
• Run specs with bundle exec rspec

Bug reports and pull requests are welcome on GitHub at https://github.com/lasseebert/kase.

This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

A pull request should consist of

• At least one failing test that proves the bug or documents the feature.
• The implementation of the bugfix or feature
• A line in the CHANGELOG.md with a description of the change, a link to your github user and, if this closes or references an issue, a link to the issue.

Find me on twitter: @lasseebert

• Noadi mimics the functional pattern matching of Elixir and might be used as an alternative of Kase.

The gem is available as open source under the terms of the MIT License.