DRY authorization with CanCanCan.

DRYing Minhas Cidades projects by wrapping common behaviours

Generates for you all YARD declarations of attributes and initializer parameters created by dry-initializer gem.

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

Destructures incoming user input onto dry struct

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.

It can successfully replace conceptually similar libraries like Dry-transaction. It's all because of the simplicity its code offers.

Kybus::Core will be used across all the kybus gems. Provides the most basic functionality or what might be used along with more than one gem. Currently this only exposes the basic exceptions and the DRY patterns.

Configuration inspired by AnywayConfig but with DryStruct DSL

This gem allows similar ActiveRecord validates_* commands to be grouped together in blocks and pruned of repeated parameters. How often have you had a block of validation commands in an ActiveRecord object that are repeated, especially :id or :unless options? Does this look familiar? validates_presence_of :hair, :hair_color, :unless => :bald? validates_length_of :hair, :within => 3..15, :unless => :bald? validates_inclusion_of :hair_color, :in => HAIR_COLORS, :unless => bald? Instead, this gem will allow you to replace the above code with: validate_block :unless => :bald? do presence_of :hair, :hair_color length_of :hair, :within => 3..15 inclusion_of :hair_color, :in => HAIR_COLORS end ..which is a great way to DRY your :hair, don't you think? Basically, this gem 1) removes the requirement to have 'validates_' on the front of the commands and 2) passes the options on the validate_block command to each validation command inside the block. The syntax of the validation commands remains the same. Keeping the 'validates_*' prefix on the commands inside the block _will_ work but it is not required.

Capistrano3 plugin for ridgepole schema application. It can handle commands: "--apply", "--dry-run", "--diff", and the other additional options

Keep a DRY history of your ActiveRecord models' changes

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

Jekyll plugin that helps you to implement the DRY (Don't Repeat Yourself) principle while writing documentation using Jekyll.

This will dry your plans.

This generator will create crud resource transactions so as to free up the developer from setting up boilerplate for them

Ant::Core will be used across all the ant gems. Provides the most basic functionality or what might be used along with more than one gem. Currently this only exposes the basic exceptions and the DRY patterns.

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.

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

DRY (Don't repeat yourself) for developing the same features over and over again. Let building your SaaS platform in a week instead of months with SaaSKit.