assertion 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 4a42bd3404b1c576172d51bb68c60070e5d0a11f
+  data.tar.gz: 652283f21156545c9aae42912cf06911e988f141
+SHA512:
+  metadata.gz: 569103f1216ac675a37aa875464c988775f6b5ed8a03150da75db092b6e44b9e35467f192091025168004d7b53efa06cc648d1b45983d6e602ff80bd0a2b63d5
+  data.tar.gz: 22d4e650d8cdd775a479e92a66eca1b3e466cd61ebc650900910c1386ba6688525b2ff2fb1edbc2fa3e6076a02059921c2f589d48f448e51c543d28eaeda719a

data/.coveralls.yml

@@ -0,0 +1,2 @@
+---
+service_name: travis-ci

data/.gitignore

@@ -0,0 +1,9 @@
+*.gem
+*.lock
+.bundle/
+.yardoc/
+coverage/
+doc/
+log/
+pkg/
+tmp/

data/.metrics

@@ -0,0 +1,9 @@
+# Settings for metric_fu and its packages are collected in the `config/metrics`
+# and loaded by the Hexx::Suit::Metrics::MetricFu.
+
+begin
+  require "hexx-suit"
+  Hexx::Suit::Metrics::MetricFu.load
+rescue LoadError
+  puts "The 'hexx-suit' gem is not installed"
+end

data/.rspec

@@ -0,0 +1,2 @@
+--require spec_helper
+--color

data/.rubocop.yml

@@ -0,0 +1,2 @@
+---
+inherit_from: "./config/metrics/rubocop.yml"

data/.travis.yml

@@ -0,0 +1,19 @@
+---
+language:     ruby
+bundler_args: --without metrics
+cache:        bundler
+rvm:
+  - '1.9.3'
+  - '2.0'
+  - '2.1'
+  - '2.2'
+  - ruby-head
+  - rbx-2 --1.9
+  - rbx-2 --2.1
+  - jruby-1.7-19mode
+  - jruby-9.0.0.0.pre2
+  - jruby-head
+matrix:
+  allow_failures:
+    - rvm: ruby-head
+    - rvm: jruby-head

data/.yardopts

@@ -0,0 +1,3 @@
+--asset LICENSE
+--exclude lib/assertion/version.rb
+--output doc/api

data/Gemfile

@@ -0,0 +1,9 @@
+source "https://rubygems.org"
+
+gemspec
+
+group :metrics do
+  gem "hexx-suit", "~> 2.2" if RUBY_ENGINE == "ruby"
+end
+
+gem "transproc", github: "solnic/transproc", branch: "registry"

data/Guardfile

@@ -0,0 +1,18 @@
+# encoding: utf-8
+
+guard :rspec, cmd: "bundle exec rspec" do
+
+  watch(%r{^spec/.+_spec\.rb$})
+
+  watch(%r{^lib/assertion/(.+)\.rb}) do |m|
+    "spec/unit/assertion/#{m[1]}_spec.rb"
+  end
+
+  watch(%r{^lib/assertion/transproc.rb}) do
+    "spec/unit/assertion/transproc"
+  end
+
+  watch("lib/assertion.rb")        { "spec" }
+  watch("spec/spec_helper.rb") { "spec" }
+
+end # guard :rspec

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2015 Andrew Kozin (nepalez), andrew.kozin@gmail.com
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,222 @@
+Assertion
+=========
+
+[![Gem Version](https://img.shields.io/gem/v/assertion.svg?style=flat)][gem]
+[![Build Status](https://img.shields.io/travis/nepalez/assertion/master.svg?style=flat)][travis]
+[![Dependency Status](https://img.shields.io/gemnasium/nepalez/assertion.svg?style=flat)][gemnasium]
+[![Code Climate](https://img.shields.io/codeclimate/github/nepalez/assertion.svg?style=flat)][codeclimate]
+[![Coverage](https://img.shields.io/coveralls/nepalez/assertion.svg?style=flat)][coveralls]
+[![Inline docs](http://inch-ci.org/github/nepalez/assertion.svg)][inch]
+
+[codeclimate]: https://codeclimate.com/github/nepalez/assertion
+[coveralls]: https://coveralls.io/r/nepalez/assertion
+[gem]: https://rubygems.org/gems/assertion
+[gemnasium]: https://gemnasium.com/nepalez/assertion
+[travis]: https://travis-ci.org/nepalez/assertion
+[inch]: https://inch-ci.org/github/nepalez/assertion
+
+Immutable assertions and validations for PORO.
+
+Synopsis
+--------
+
+The primary goal of the gem is to decouple assertions about the objects, and their validations, from the data.
+
+No `ActiveSupport`, no mutation of any instances.
+
+### Basic Usage
+
+Define the assertion by inheriting it from the `Assertion::Base` class with attributes to which it should be applied.
+Then implement the method `check` that should return the boolean value.
+
+You can do it either in a classic style:
+
+```ruby
+class IsAdult < Assertion::Base
+  attribute :age, :name
+
+  def check
+    age >= 18
+  end
+end
+```
+
+or using a builder for verbosity with the same result:
+
+```ruby
+IsAdult = Assertion.about :age, :name do
+  age >= 18
+end
+```
+
+Define translations for both the *right* and *wrong* states of the assertion.
+
+All the declared attributes are available (that's why we declared a `name` as an attribute):
+
+```yaml
+# config/locales/en.yml
+---
+en:
+  assertion:
+    is_adult:
+      right: "%{name} is already an adult (age %{age})"
+      wrong: "%{name} is a child yet (age %{age})"
+```
+
+Check a state of a assertion for some argument(s), using class method `[]`:
+
+```ruby
+john = { name: 'John', age: 10, gender: :male }
+
+state = IsAdult[john]
+# => #<Assertion::State @state=false, @messages=["John is a child yet (age 10)"]>
+```
+
+The state supports `valid?`, `invalid?`, `messages` and `validate!` methods:
+
+```ruby
+state.valid?    # => false
+state.invalid?  # => true
+state.messages  # => ["John is a child yet (age 10)"]
+state.validate! # => #<Assertion::InvalidError @messages=["John is a child yet (age 10)"]>
+```
+
+### Assertion Inversion
+
+Use the `.not` *class* method to negate a assertion:
+
+```ruby
+jack = { name: 'Jack', age: 21, gender: :male }
+
+IsAdult.not[jack]
+# => #<Assertion::State @state=false, @messages=["Jack is already an adult (age 21)"]>
+```
+
+### Composition of States
+
+You can compose assertion states (results):
+
+```ruby
+IsMale = Assertion.about :name, :gender do
+  gender == :male
+end
+```
+
+```yaml
+# config/locales/en.yml
+---
+en:
+  assertion:
+    is_male:
+      right: "%{name} is a male"
+      wrong: "%{name} is a female"
+```
+
+Use method `&` (or its aliases `+` or `>>`) to compose assertion states:
+
+```ruby
+jane = { name: 'Jane', age: 16, gender: :female }
+
+state = IsAdult[jane] & IsMale[jane]
+# => #<Assertion::State @state=false, @messages=["Jane is a child yet (age 16)", "Jane is a female"]>
+```
+
+Object Validation
+-----------------
+
+If you are used to "rails style" validations, provide a validator from assertions:
+
+```ruby
+class User
+  include Virtus.model
+
+  attribute :name, String
+  attribute :age, Integer
+  attribute :gender, Symbol
+end
+
+class Women < User
+  def validate!
+    state.validate!
+  end
+
+  def state
+    IsAdult[attributes] & IsMale.not[attributes]
+  end
+end
+
+judy = Women.new(name: "Judy", age: 15, gender: :female)
+judy.valdate!
+# => #<Assertion::InvalidError @messages=["Judy is a child yet (age 15)"]>
+```
+
+Edge Cases
+----------
+
+You're expected to declare the `check` method for the assertion before applying it to some data.
+
+Otherwise `Assertion::NotImplementedError` is raised:
+
+```ruby
+IsAdult = Assertion.about :name, :age
+
+IsAdult[name: "Jane", age: 10]
+# => #<Assertion::NotImplementedError @message="IsAdult#check method not implemented">
+```
+
+You cannot define attributes with names, that are already used as an istance methods:
+
+```ruby
+IsAdult = Assertion.about :check, :call
+# => #<Assertion::NameError @message="Wrong name(s) for attribute(s): check, call">
+```
+
+Installation
+------------
+
+Add this line to your application's Gemfile:
+
+```ruby
+# Gemfile
+gem "assertion"
+```
+
+Then execute:
+
+```
+bundle
+```
+
+Or add it manually:
+
+```
+gem install assertion
+```
+
+Compatibility
+-------------
+
+Tested under rubies [compatible to MRI 1.9+](.travis.yml).
+
+Uses [RSpec] 3.0+ for testing and [hexx-suit] for dev/test tools collection.
+
+[RSpec]: http://rspec.org
+[hexx-suit]: https://github.com/nepalez/hexx-suit
+
+Contributing
+------------
+
+* Read the [STYLEGUIDE](config/metrics/STYLEGUIDE)
+* [Fork the project](https://github.com/nepalez/assertion)
+* Create your feature branch (`git checkout -b my-new-feature`)
+* Add tests for it (please, use [mutant] to verify the coverage!)
+* Commit your changes (`git commit -am '[UPDATE] Add some feature'`)
+* Push to the branch (`git push origin my-new-feature`)
+* Create a new Pull Request
+
+[mutant]: https://github.com/mbj/mutant
+
+License
+-------
+
+See the [MIT LICENSE](LICENSE).

data/Rakefile

@@ -0,0 +1,29 @@
+# encoding: utf-8
+begin
+  require "bundler/setup"
+rescue LoadError
+  puts "You must `gem install bundler` and `bundle install` to run rake tasks"
+  exit
+end
+
+# Loads bundler tasks
+Bundler::GemHelper.install_tasks
+
+# Loads the Hexx::RSpec and its tasks
+begin
+  require "hexx-suit"
+  Hexx::Suit.install_tasks
+rescue LoadError
+  require "hexx-rspec"
+  Hexx::RSpec.install_tasks
+end
+
+# Sets the Hexx::RSpec :test task to default
+task :default do
+  system "bundle exec rspec spec"
+end
+
+desc "Runs mutation metric for testing"
+task :mutant do
+  system "mutant -r ./spec/spec_helper --use rspec 'Assertion*' --fail-fast"
+end

data/assertion.gemspec

@@ -0,0 +1,27 @@
+$:.push File.expand_path("../lib", __FILE__)
+require "assertion/version"
+
+Gem::Specification.new do |gem|
+
+  gem.name        = "assertion"
+  gem.version     = Assertion::VERSION.dup
+  gem.author      = "Andrew Kozin"
+  gem.email       = "andrew.kozin@gmail.com"
+  gem.homepage    = "https://github.com/nepalez/assertion"
+  gem.summary     = "PORO assertions and validation"
+  gem.license     = "MIT"
+
+  gem.files            = `git ls-files`.split($INPUT_RECORD_SEPARATOR)
+  gem.test_files       = Dir["spec/**/*.rb"]
+  gem.extra_rdoc_files = Dir["README.md", "LICENSE"]
+  gem.require_paths    = ["lib"]
+
+  gem.required_ruby_version = "~> 1.9"
+
+  gem.add_runtime_dependency "transproc", "~> 0.2"
+  gem.add_runtime_dependency "i18n", "~> 0.7"
+
+  gem.add_development_dependency "hexx-rspec", "~> 0.4"
+  gem.add_development_dependency "equalizer", "~> 0.0"
+
+end # Gem::Specification

data/config/metrics/STYLEGUIDE

@@ -0,0 +1,230 @@
+= Ruby Style Guide
+
+Adapted from Dan Kubb's Ruby Style Guide
+https://github.com/dkubb/styleguide/blob/master/RUBY-STYLE
+
+== Commiting:
+
+* Write descriptive commit messages, following the pattern:
+
+    [TYPE] name
+
+    The message, describing the changes being made
+
+* Use the types below to mark commits:
+
+  - FEATURE - for adding new features, or backward-compatible changes;
+  - CHANGE - for backward-incompatible changes;
+  - BUG FIX - for fixing bugs;
+  - REFACTORING - for other changes of the code not affecting the API;
+  - OTHER - for changes in documentaton, metrics etc, not touching the code;
+  - VERSION - for version changes.
+
+* Always separate commits of different types (such as FEATURE and CHANGE).
+
+* Try to separate various features from each other.
+
+* Include specification to the same commit as the code.
+
+* Run all tests before making a commit.
+  Never commit the code that break unit tests.
+
+* Use metric (run `rake check`) before making a commit.
+
+* Do refactoring before making a commit. Best writing is rewriting.
+
+* Follow semantic versioning.
+
+    http://semver.org/
+
+* For versions name the commit after a version number, following the pattern:
+
+    VERSION 1.0.0-rc2
+
+
+== Formatting:
+
+* Use UTF-8. Declare encoding in the first line of every file.
+
+    # encoding: utf-8
+
+* Use 2 space indent, no tabs.
+
+* Use Unix-style line endings.
+
+* Use spaces around operators, after commas, colons and semicolons,
+  around { and before }.
+
+* No spaces after (, [ and before ], ).
+
+* Align `when` and `else` with `case`.
+
+* Use an empty line before the return value of a method (unless it
+  only has one line), and an empty line between defs.
+
+* Use empty lines to break up a long method into logical paragraphs.
+
+* Keep lines fewer than 80 characters.
+
+* Strip trailing whitespace.
+
+
+== Syntax:
+
+* Write for 2.0.
+
+* Use double quotes
+  
+    http://viget.com/extend/just-use-double-quoted-ruby-strings
+
+* Use def with parentheses when there are arguments.
+
+* Never use for, unless you exactly know why.
+
+* Never use then, except in case statements.
+
+* Use when x then ... for one-line cases.
+
+* Use &&/|| for boolean expressions, and/or for control flow. (Rule
+  of thumb: If you have to use outer parentheses, you are using the
+  wrong operators.)
+
+* Avoid double negation (!!), unless Null Objects are expected.
+  
+    http://devblog.avdi.org/2011/05/30/null-objects-and-falsiness
+
+* Avoid multiline ?:, use if.
+
+* Use {...} when defining blocks on one line. Use do...end for multiline
+  blocks.
+
+* Avoid return where not required.
+
+* Use ||= freely.
+
+* Use OO regexps, and avoid =~ $0-9, $~, $` and $' when possible.
+
+* Do not use Enumerable#inject when the "memo" object does not change between
+  iterations, use Enumerable#each_with_object instead (in ruby 1.9,
+  active_support and backports).
+
+* Prefer ENV.fetch to ENV[] syntax.
+  Prefer block syntax for ENV.fetch to usage of the second argument.
+
+
+== Naming:
+
+* Use snake_case for methods.
+
+* Use CamelCase for classes and modules. (Keep acronyms like HTTP,
+  RFC, XML uppercase.)
+
+* Use SCREAMING_SNAKE_CASE for other constants.
+
+* Do not use single letter variable names. Avoid uncommunicative names.
+
+* Use consistent variable names. Try to keep the variable names close
+  to the object class name.
+
+* Use names prefixed with _ for unused variables.
+
+* When defining a predicate method that compares against another object of
+  a similar type, name the argument "other".
+
+* Prefer map over collect, detect over find, select over find_all.
+
+* Use def self.method to define singleton methods.
+
+* Avoid alias when alias_method will do.
+
+
+== Comments:
+
+* Use YARD and its conventions for API documentation. Don't put an
+  empty line between the comment block and the def.
+
+* Comments longer than a word are capitalized and use punctuation.
+  Use one space after periods.
+
+* Avoid superfluous comments.
+
+
+== Code structuring:
+
+* Break code into packages, decoupled from the environment.
+
+* Wrap packages into gems.
+
+* Inject dependencies explicitly.
+  Leave all outer references on the border of any package. Inside
+  the package use internal references only.
+
+* Follow SOLID principles.
+
+    http://en.wikipedia.org/wiki/SOLID_(object-oriented_design)
+
+* Only give a method one purpose for existing. If you pass in a boolean
+  to a method, what you're saying is that this method has two different
+  behaviours. Just split it into two single purpose methods. If you have
+  to use the words "AND" or "OR" to describe what the method does it
+  probably does too much.
+
+* Avoid long methods.
+  Try to keep them at no more than 6 lines long, and preferably 4 or less.
+
+  If sections of a method are logically separate by blank lines, then
+  that's probably a sign that those sections should be split into separate
+  methods.
+
+* Avoid hashes-as-optional-parameters. Does the method do too much?
+
+* Avoid long parameter lists.
+
+* Add "global" methods to Kernel (if you have to) and make them private.
+
+* Use OptionParser for parsing complex command line options and
+  ruby -s for trivial command line options.
+
+* Avoid needless metaprogramming.
+
+* Always freeze objects assigned to constants.
+
+
+== General:
+
+* Code in a functional way, avoid mutation when it makes sense.
+
+* Try to have methods either return the state of the object and have
+  no side effects, or return self and have side effects. This is
+  otherwise known as Command-query separation (CQS):
+
+    http://en.wikipedia.org/wiki/Command-query_separation
+
+* Do not mutate arguments unless that is the purpose of the method.
+
+* Try following TRUE heuristics by Sandi Metz
+
+    http://designisrefactoring.com/2015/02/08/introducing-sandi-metz-true/
+
+* Do not mess around in core classes when writing libraries.
+  Namespace your code inside the modules, or wrap core classes to
+  decorators of your own.
+
+* Do not program defensively.
+  
+    http://www.erlang.se/doc/programming_rules.shtml#HDR11
+
+* Keep the code simple.
+
+* Don't overdesign.
+
+* Don't underdesign.
+
+* Avoid bugs.
+
+* Read other style guides and apply the parts that don't dissent with
+  this list.
+
+* Be consistent.
+
+* Use common sense.