Fix::Let

Build Status Gem Version Inline docs Documentation

Provides let method for memoized helper definition.

Contact

Rubies

Installation

Fix::Let is cryptographically signed.

To be sure the gem you install hasn't been tampered with, add my public key (if you haven't already) as a trusted certificate:

$ gem cert --add <(curl -Ls https://raw.github.com/fixrb/fix-let/master/certs/gem-fixrb-public_cert.pem)
$ gem install fix-let -P HighSecurity

The HighSecurity trust profile will verify all gems. All of Fix::Let's dependencies are signed.

Or add this line to your application's Gemfile:

gem 'fix-let'

And then execute:

$ bundle

Let's get started!

asciicast

Usage

Given this code:

# duck_spec.rb

require 'fix/let'

class Duck
  def swims
    'So! Swoosh...'
  end
end

Fix.describe Duck.new do
  let(:famous_word) { 'So!' }

  on :swims do
    it { MUST eql "#{famous_word} Swoosh..." }
  end
end

The output should look like this:

$ ruby duck_spec.rb
.

Ran 1 tests in 0.000243 seconds
100% compliant - 0 infos, 0 failures, 0 errors

Security

As a basic form of security Fix::Let provides a set of SHA512 checksums for every Gem release. These checksums can be found in the checksum/ directory. Although these checksums do not prevent malicious users from tampering with a built Gem they can be used for basic integrity verification purposes.

The checksum of a file can be checked using the sha512sum command. For example:

$ sha512sum pkg/fix-let-0.1.0.gem
26198b7812a5ac118a5f2a1b63927871b3378efb071b37abb7e1ba87c1aac9f3a6b45eeae87d9dc647b194c15171b13f15e46503a9a1440b1233faf924381ff5  pkg/fix-let-0.1.0.gem

Versioning

Fix::Let follows Semantic Versioning 2.0.

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 a new Pull Request

License

See LICENSE.md file.

This project is sponsored by:

Sashite