Write haml views once, and then use them for both server and clientside rendering (using automagically precompiled handlebars templates)

Several additions for DRYer RSpec code

Create Elasticsearch models and mappings from code.

Adds functionality to make dry-types/dry-struct play nicely with graphql-ruby

Applications that have complex email sending logic have DRYness problems. ActiveMailer solves that by making a legitimate email model where all sending logic belongs. It is also capable of acting as an audit trail for email sending.

Keep your code DRY by inferring column validations from table properties! Automagically validate presence, length, numericality, inclusion and uniqueness of ActiveRecord backed columns.

A simple way for DRYier, faster and cleaner Modernizr tests in Sass.

Flexible DRY validations with API docs generation done right TLDR; parametrics on steroids.

A series of helpful sugar of the Chef core and other resources to make a cleaner, more lean recipe DSL, enforce DRY principles, and make writing Chef recipes an awesome experience!

A CLI (as in Command Line Interface) to delete your tweets based on faves, RTs, and time. There are some services out there with a friendly web interface, but this is not one of them. You must know the basics of working with a UNIX terminal and configuring a Twitter API app, as this will only work if you have a Twitter Developer account. Due to the irrevocable nature of tweet deletion, all delete commands are dry-run true, meaning you must call all of them with a --dry-run=false flag if you want them to really do something. Called with --dry-run=false, there is no way to revoke tweet deletion. They are just gone, disappeared into the ether (or the stashed in the Twitter-owned secret place you have no access to without a mandate since nothing gets really deleted from the web these days, folks). This tool won't delete all of your tweets in one fell swoop; it is more of a way to delete your old tweets from time to time. The Twitter API rate limits are relatively complicated, and I don't even wanna go there, but if you do intend on deleting all of your tweets, you can do it with this CLI and some perseverance. I did delete more than 100k of mine by using this script every day for a couple of weeks. The more tweets you delete, the fewer of them you have, and with time the rate limits won't be that much of a problem. I Delete My Tweets (IDMT) can delete your tweets by fetching them via API using an APP you will have to set up yourself. Still, it can also delete tweets from an CSV (comma-separated file) that you can generate from the archive you can request from twitter.com by going to Settings and privacy > Your Account > Download an archive of your data. It is out of the scope of this CLI to generate the CSV (at the moment) but there are scripts out there that can do this for you.

imap-filter is a Ruby implementation of an IMAP filtering application. it can handle multiple IMAP accounts, and create IMAP folders automatically where none exists. The imap-filter DSL makes it easy to filter. You can also do "dry-runs" to make sure what happens is what is expected.

Keep a DRY multilingual translation of your ActiveRecord models' textual attributes

Provides some useful modules, classes, and methods for FFI bindings as well as a DSL-like syntax for FFI::Struct layouts

A gem for pointing out redundant css

Adds ActiveRecord-specific methods to Dry::Initializer

A Dockerfile-replacement DSL for building complex images

dry-rails provides the official integration of dry-rb gems with Ruby on Rails framework.

Using Inherited Resources is an excellent way to reduce the amount of repetition in your controllers. But what about views? A lot of times resources share the same views, so why not DRY 'em up using Inherited Resources Views!

Dry-matcher free implementation of trailblazer endpoint, with ability to redefine matchers and handlers behavior for separate controllers or actions.

Normalize dry-validation and ActiveModel errors to the universal format