Helpful aliases for Object#taint
Ruby
Latest commit 3657d1e Feb 19, 2014 @canweriotnow canweriotnow Update README.md
Permalink
Failed to load latest commit information.
lib Update README, bump version Jan 24, 2014
spec Add specs for untaints and taint queries Jan 24, 2014
.gitignore First commit Jan 23, 2014
.rspec
Gemfile
LICENSE.txt
README.md
Rakefile First commit Jan 23, 2014
taint_aliases.gemspec

README.md

TaintAliases

Build Status Code Climate Coverage Status Dependency Status Gem Version

Aliases Object#taint with other common idioms for taint, such as #grundle and #fleshy_fun_bridge

Installation

Add this line to your application's Gemfile:

gem 'taint_aliases', require: true

And then execute:

$ bundle

Or install it yourself as:

$ gem install taint_aliases

Usage

Just require taint_aliases, or require in your Gemfile; then you can do this:

obj = Object.new
obj.grundle

obj.tainted?
=> true

str = "Test String"
str.fleshy_fun_bridge

str.tainted?
=> true

It's that easy!

taint_aliases currently supplies the following methods to taint your objects:

  • grundle
  • fleshy_fun_bridge
  • perineum
  • gouch
  • gooch
  • grundel

Thanks to threeifbywhiskey, you can now use equivalent methods to untaint and check the taintedness of your objects, e.g.:

obj = Object.new
obj.grundle

obj.grundled?
=> true

obj.unperineum

obj.fleshy_fun_bridged?
=> false

Contributors

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License

Copyright © 2014 Jason Lewis, Micah Gates

Distributed under the MIT License; see LICENSE.txt