A little over a year ago, I discovered Trailblazer and used its concept of "operations" in a few projects. While I came to enjoy their concept of pipelines and result objects, I felt the entire project was entirely too complex for my use cases. I wanted much simpler pipelines and nesting.
Gem names are hard to come by these days. I'd considered something slightly more mature like half_pipe, but in the age of appending a codes of conduct to projects, I lean offensive in naming wherever possible. I'm kinda wishing I had named my factory gem meth_lab instead.
Pretty standard gem stuff.
$ gem install crack_pipe
If you're using Bundler (and who isn't?) it's likely you'll add this to your Gemfile like so:
gem 'crack_pipe'
One day I'll write some actual documentation. (Yeah, right.) In the meantime, the action spec has a pretty good example of steps, always passing, fail tracks, short circuiting, and nesting actions.
GitHub issues are for bugs, not support. As of right now, there is no official support for this gem. You can try reaching out to the author, Joshua Hansen if you're really stuck, but there's a pretty high chance that won't go anywhere at the moment or you'll get a response like this:
Hi. I'm super busy. It's nothing personal. Check the README first if you haven't already. If you don't find your answer there, it's time to start reading the source. Have fun! Let me know if I screwed something up.
- Include tests with your PRs.
Don't smoke crack.
See LICENSE.txt.
The codebase is pretty small. That was one of the main design goals. If you can figure out how to use it, I'm sure you can maintain it.