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

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! [Forked by Combell SRE for Chef 16]

String inflections for dry-rb

SchemaValidations extends ActiveRecord to automatically create validations by inspecting the database schema. This makes your models more DRY as you no longer need to duplicate NOT NULL, unique, numeric and varchar constraints on the model level.

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 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!

Common framework to build command line interfaces with Ruby

Common framework to build command line interfaces with Ruby

Module to define equality, equivalence and inspection methods

Pub/sub system

Custom dry-types to ensure type safety

DRY module for APIs to render HTTP errors in JSON

Algebraic effects

SchemaAssociations extends ActiveRecord to automatically create associations by inspecting the database schema. This is more more DRY than the standard behavior, for which in addition to specifying the foreign key in the migration, you must also specify complementary associations in two model files (e.g. a :belongs_to and a :has_many).

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.

Data transformation toolkit

DRYing Minhas Cidades projects by wrapping common behaviours

DRYing Our Cities projects by wrapping common behaviours

Cache responses in HTTParty models

ActionParameter helps you move all your parameter's logic into it's own class. This way you'll keep your controllers dry and they would be easier to test.