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

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

Save keystrokes with OptionParser while using more or less the same API.

DRYing Our Cities projects by wrapping common behaviours

Implements a DRY front end for Ruby on Rails: routes, controllers, and views...

Run tests on change in a docker container continuously

Cushion your attributes. Return a static or dynamic default if your @variable isn’t defined. DRY off your code.

The ultimate DRY and fast solution to managing any kind of test data. Based on Blueprints.

DRYing Minhas Cidades projects by wrapping common behaviours

This gem provides a set of modules and methods to help quickly and DRYly create a test automation framework using Ruby and Watir (or watir-webdriver).

This gem provides a set of modules and methods to help quickly and DRYly create a test automation framework using Ruby and Watir (or watir-webdriver).

Cache responses in HTTParty models

You don't want to type with wet hands, but you're not near any towels. What to do? Use the airblade gem to dry your hands straight from your Mac's terminal!

You don't want to type with wet hands, but you're not near any towels. What to do? Use the airblade gem to dry your hands straight from your Mac's terminal!

Where Conditioner allows you to write conditional `where` expressions in a DRY manner.

DRY in swagger and roar scenario, generate documentation from roar modelss

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.

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.

Cruddy is intended to DRY up basic CRUD in rails controllers.

Keep a DRY history of your ActiveRecord models' changes