It provides a dried PORO of OpenAPI specification.

collection of often used cucumber steps to avoid the violation of DRY principle

Enables easy and DRY code timing capabilities.

Custom dry-types to ensure type safety

A cleaner and DRYer alternative to mocking and stubbing with RSpec, using Arrange-Act-Assert syntax

Dryad core includes the basic objects.

Dryad consul is the adapter for consul.

DRY controller actions for Rails > 3.0 and keeps your controllers nice and skinny.

web_pipe integration for dry-web apps

A lightweight Object-Relational Mapping (ORM) library for Ruby. Allows you to keep code DRY and easily perform database operations in an object-oriented manner.

An implementation of the command pattern using dry-rb

DRY-up Rails controllers by leveraging interchangeable conductors to export data

micro library to dry models

Dryad is a configration management client. It provides functions such as hot loading of configuration files.

A DRY approach to unit conversion. Define rules, make soup, convert.

DRY-up Rails controllers by leveraging interchangeable conductors to export data

Dry::Structs with swagger

There are tons of books yelling about how you shouldn't repeat yourself, how you should keep it DRY(Don't Repeat Yourself). Well, we tried hard to keep the code clean, but when it comes to blog we wrote, we seems quite ignorante to the DRY principle. During the whole developement process, there will always be some interesting points you want to record, so git gurus told us to write proper git commit messages for further reference or so. And yes, I followed, and I spent quite a time writing about the problem I encountered, how I found the solution, and what should might be useful in the future. That's nice, right? But I've also got a blog to write! Wait, I don't want to REPEAT MYSELF. And that leads to a barely touched blog site. And git-blog is here to help.

Dry::Types for RSpec

The gems enables you to use Fear::Option as optional type for Dry::Types