what-we-ve-got-here-is-an-error-to-communicate
What if Ruby's error messages communicated their information effectively?
Ecosystems:
Ruby
What if error messages were compelling to read?
Blog explaining the goal here.
A screenshot of the code rendering an ArgumentError.
This is still early and Rough
But I've been using it on its own test suite, and have to say it's compelling!
Using this with RSpec or Minitest
Place this in your .rspec file to use with RSpec. Or just use MRspec, which works with both RSpec and Minitest and requires no configuration :)
--colour
--require error_to_communicate/at_exit
--require error_to_communicate/rspec_formatter
--format WhatWeveGotHereIsAnErrorToCommunicate::RSpecFormatter
Inspirations:
- I think initially this was inspired by Sarah Gray's talk at Software Craftsmanship North America:
Visualizing Enumerable: Own Abstract Concepts Through Physicalization - Got to thinking about it again with Kerri Miller, conversing at DCamp,
and then at Ruby Conf, she created chatty_exceptions
which is in this same domain.
Related Projects:
- Charlie Sommerville's better_errors
gem gives you a nice interface like this for Rails. - Koichi's pretty_backtrace
License
Package Rankings
Top 15.48% on Rubygems.org