Sha256: 7aeb3c9076e56aca158ecdc54863c349e6dd6489c6407500fea7546cfec8452a

Contents?: true

Size: 1.66 KB

Versions: 1

Compression:

Stored size: 1.66 KB

Contents

lib = File.expand_path("../lib", __FILE__)
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
require "boolean_timestamp/version"

Gem::Specification.new do |spec|
  spec.name          = "boolean_timestamp"
  spec.version       = BooleanTimestamp::VERSION
  spec.authors       = ["Mo Lawson"]
  spec.email         = ["moklawson@gmail.com"]

  spec.summary       = %q{The precision of a timestamp column with the API of a boolean column}
  spec.description   = %q{True/False fields have a great simplicity about them, and many times
  they're perfect for the job! But, it's not uncommon end up in a place where you'd really love to
  keep some degree of simplicity with a little more detail about when the value was changed.
  Sometimes you'll want to display that information to the user and other times you'll keep it for
  auditing or debugging purposes. Either way, boolean_timestamp makes the job easy from the
  beginning and adds very little code to your app.}
  spec.homepage      = "https://github.com/molawson/boolean_timestamp"
  spec.license       = "MIT"

  # Specify which files should be added to the gem when it is released.
  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
  end
  spec.bindir        = "exe"
  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
  spec.require_paths = ["lib"]

  spec.add_development_dependency "bundler", "~> 1.16"
  spec.add_development_dependency "rake", "~> 10.0"
  spec.add_development_dependency "rspec", "~> 3.0"
end

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
boolean_timestamp-0.1.0 boolean_timestamp.gemspec