Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
A tiny debugging library for Ruby
Ruby
Tree: 2bb9e6eb4b

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
lib
spec
.gitignore
COPYING
Gemfile
README.md
letters.gemspec

README.md

Letters is a little alphabetical library that makes sophisticated debugging easy & fun.

Quick note about Rails: Until I build a Rails-specific gem, I'm changing Letters to patch Object by default. To only patch core classes, require "letters/patch/core". For Rails support, require "letters/patch/rails". Make sure to do this after Bundler.require in application.rb.

For many of us, troubleshooting begins and ends with the print statement. Others recruit the debugger, too. (Maybe you use print statements to look at changes over time but the debugger to focus on a small bit of code.) These tools are good, but they are the lowest level of how we can debug in Ruby. Letters leverages print, the debugger, control transfer, computer beeps, and other side-effects for more well-rounded visibility into code and state.

Installation

If you're using RubyGems, install Letters with:

gem install letters

By default, requiring "letters" monkey-patches Object. It goes without saying that if you're using Letters in an app that has environments, you probably only want to use it in development.

Debugging with letters

With Letters installed, you have a suite of methods available wherever you want them in your code -- at the end of any expression, in the middle of any pipeline. Most of these methods will output some form of information, though there are more sophisticated ones that pass around control of the application.

There are almost 20 Letters methods so far. You can find them in the documentation.

Let's use with the p method as an example. It is one of the most familiar methods. Calling it prints the receiver to STDOUT and returns the receiver:

{ foo: "bar" }.p 
# => { foo: "bar" }
# prints { foo: "bar" }

That's simple enough, but not really useful. Things get interesting when you're in a pipeline:

words.grep(/interesting/).
  map(&:downcase).
  group_by(&:length).
  values_at(5, 10).
  slice(0..2).
  join(", ")

If I want to know the state of your code after lines 3 and 5, all I have to do is add .p to each one:

words.grep(/interesting/).
  map(&:downcase).
  group_by(&:length).p.
  values_at(5, 10).
  slice(0..2).p.
  join(", ")

Because the p method (and nearly every Letters method) returns the original object, introducing it is only ever for side effects -- it won't change the output of your code.

This is significantly easier than breaking apart the pipeline using variable assignment or a hefty tap block.

The p method takes options, too, so you can add a prefix message to the output or choose another output format -- like YAML or pretty print.

Something went wrong with that request. Please try again.