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.

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 fi...

Dry::Types typedefs found to be generally useful. Replaces deprecated prolog-dry-types.

A parser which converts dry-struct schema into a readable hash for further manipulation

Adds ActiveRecord-specific methods to Dry::Initializer

Dryad consul is the adapter for consul.

A gem to standardize our use of Dry-RB

Manage and deploy secrets (access keys, API tokens etc) in encrypted files which can safely be committed to the code repository. To decrypt and and use them, only one environment variable containing the corresponding key is required. While similar to ActiveSupport::EncryptedConfiguration, this l...

Keep a DRY history of your ActiveRecord models' changes

RSpec `have_attribute` matcher for dry-struct gem

Dessribe structure, validate and coerce values. Powered by dry-types and dry-struct

A set of Jets responders to dry up your application

A light attributes wrapper for dry-initializer. Forked from "https://github.com/goldstar/artisanal-model"

DRY your controllers and make your API more predictable by defining responders for different formats. E.g. Posting an invalid resource in HTML should render a form with errors, while in JSON you expect serialized errors.

A complete, standalone view rendering system that gives you everything you need to write well-factored view code

Use cluster for service discovery. Use round robin to process scheduling.

The Tuple type implementation for Dry::Types.

Pipeline operator for callable objects

Automatic JSON:API for dry_crud applications

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!