schemad 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 42533ea7f5721acf5f2bcc3c10a10322b61d6e76
-  data.tar.gz: d24a50de59c6ce8d81d5c5466f19b993e05bfe06
+  metadata.gz: d65d60e8c0d2976ed42bd8ab10ebaed58f4e1010
+  data.tar.gz: 74d74e0511eb3accaaebd48c240d05b4e0f33f89
 SHA512:
-  metadata.gz: 9cced2f7ca522ac55286b5c34e7ab1539a342c16c97831cbeb838987f1885790dd81d2bc73a80f4783d166ef5bbc0258a5fc61cf8fab9c97befe6c812dd9f1a6
-  data.tar.gz: c828d9d9c9c0ab5e7df1d50613ec45c63f7d13f91ac5cb7db404a896f2158b63a9270580ba3b41707c3a46020ae586d898c53e462a3b69a97db3a3c02b3a2998
+  metadata.gz: b085350cfd29b11fd7e9e535256b67c774afc0b90ccfc44999a024a1d84ea85b191d56b1896d751e20f1a4e80a68c0654c180d9fad2035badceadd1511ab5450
+  data.tar.gz: 969ceaef8a69f3e951d2da2583138551d72e5d9c948e41a32704785b21c1ebeb77eba05cb36feae7ccda61aa67c8f15695ec2b3711353c3fed64308746509254

data/.travis.yml

@@ -0,0 +1,14 @@
+language: ruby
+rvm:
+  - 2.0
+  - 2.1
+  - 1.9.3
+  - rbx
+  - jruby-19mode
+
+matrix:
+  allow_failures:
+    - rvm: rbx
+    - rvm: jruby-19mode
+
+script: bundle exec rake spec

data/README.md

@@ -1,12 +1,15 @@
 # Schemad
 
+[![Gem Version](https://badge.fury.io/rb/schemad.svg)](http://badge.fury.io/rb/schemad)
+[![Build Status](https://travis-ci.org/plukevdh/schemad.svg?branch=master)](https://travis-ci.org/plukevdh/schemad)
+
 Schemad is a simple metagem to aid integrating legacy or third-party datasets into other projects. It's especially geared towards unifying multiple datasets into consistent data structures for ease of and consistency in use.
 
 This gem has two main parts: Normalizers and Entities.
 
 ## Normalizers
 
-Normalizers are the translators between different datasets. They take misshaped data and help mold it into a consistent form before turning them into objects for general use. 
+Normalizers are the translators between different datasets. They take misshaped data and help mold it into a consistent form before turning them into objects for general use.
 
 For example, let's say I want to pull commit data from [GitHub](https://github.com) and [BitBucket](https://bitbucket.org) and do something with the two datasets. Let's look at the API for both and the kind of data they return for a commit object.
 
@@ -167,7 +170,7 @@ github_data = JSON.parse(raw_json)
 parsed = GitHubNormalizer.new.normalize(github_data)
 ```
 
-And we should then have a plain hash much like the following: 
+And we should then have a plain hash much like the following:
 
 ```ruby
 {
@@ -205,7 +208,7 @@ Now the normalizer will use the raw field and pick out the email using a regex m
 
 ## Entities
 
-Entities provide consistent [value objects](http://martinfowler.com/bliki/ValueObject.html) that allow for easily transporting the data to functionality that uses the data. Entities are very limited in functionality and are mainly meant to provide a more ruby-ish means of accessing the data. We _could_ pass around the normalized hashes, but typically, we rubyists like having method access to our data: 
+Entities provide consistent [value objects](http://martinfowler.com/bliki/ValueObject.html) that allow for easily transporting the data to functionality that uses the data. Entities are very limited in functionality and are mainly meant to provide a more ruby-ish means of accessing the data. We _could_ pass around the normalized hashes, but typically, we rubyists like having method access to our data:
 
 ```ruby
 commit.comment        # "added readme, because im a good github citizen\n"
@@ -213,7 +216,7 @@ commit.id             # "7638417db6d59f3c431d3e1f261cc637155684cd"
 comment.created_date  # A time object!
 ```
 
-So this is what Entities provide. 
+So this is what Entities provide.
 
 ```ruby
 class Commit < Schemad::Entity
@@ -233,6 +236,8 @@ Note that the default attribute type (if not provided) is a string (`:string`).
 - :integer
 - :boolean
 
+To get these types, simply `require 'schemad/default_types'`. They are not required by default to ensure that my Schemad's type handling is what you want explicity.
+
 New types are easy to create, more on this in a moment.
 
 To instantiate these new class, we use the `from_data` method to ensure parsing with the output from the normalizer step above:
@@ -252,7 +257,7 @@ comment.created_date  # A time object!
 
 You don't have to use the normalizers to use the `from_data` method. It can be any consistently formatted hash. The keys **must** be accessible by symbol however (use a hash with all symbols as keys or an ActiveSupport/Hashie/other [HashWithIndifferentAccess](http://api.rubyonrails.org/classes/ActiveSupport/HashWithIndifferentAccess.html) implementation).
 
-In fact, both normalizer and entity can be used independent of one another if one or the other isn't required for your use. Just include the library you want: 
+In fact, both normalizer and entity can be used independent of one another if one or the other isn't required for your use. Just include the library you want:
 
 ```ruby
 require 'schemad/type_handler'

data/lib/schemad/default_types.rb

@@ -0,0 +1,5 @@
+require 'schemad/types/boolean_handler'
+require 'schemad/types/integer_handler'
+require 'schemad/types/string_handler'
+require 'schemad/types/time_handler'
+

data/lib/schemad/version.rb

@@ -1,3 +1,3 @@
 module Schemad
-  VERSION = "1.0.0"
+  VERSION = "1.0.1"
 end

data/lib/schemad.rb

@@ -1,6 +1,7 @@
 require "schemad/version"
 
 require 'schemad/type_handler'
+require 'schemad/default_types'
 require 'schemad/normalizer'
 require 'schemad/entity'
 

data/spec/entity_spec.rb

@@ -23,7 +23,7 @@ describe Schemad::Entity do
     context "defaults or nil get used when no data" do
 
       Then { ent.forest.should == "Green" }
-      And { ent.cool.should be_true }
+      And { ent.cool.should eq true }
       And { ent.created.should eq(Time.now) }
       And { ent.roads.should == 5 }
       And { ent.world.should == "coordinates" }

data/spec/type_handler_spec.rb

@@ -41,14 +41,14 @@ describe Schemad::TypeHandler do
     context "knows trues" do
       Schemad::BooleanHandler::VALID_TRUTHS.each do |val|
         When(:parsed) { bool_handler.parse(val) }
-        Then { parsed.should be_true }
+        Then { parsed.should eq true }
       end
     end
 
     context "rejects falses" do
       [42, "Hello World", nil, String].each do |val|
         When(:parsed) { bool_handler.parse(val) }
-        Then { parsed.should be_false }
+        Then { parsed.should eq false }
       end
     end
   end
@@ -122,4 +122,4 @@ describe Schemad::TypeHandler do
       Then { result.to_i.should == date_time.to_time.to_i }
     end
   end
-end
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: schemad
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Luke van der Hoeven
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-05-08 00:00:00.000000000 Z
+date: 2015-01-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -62,12 +62,14 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".gitignore"
+- ".travis.yml"
 - Gemfile
 - LICENSE.txt
 - README.md
 - Rakefile
 - lib/schemad.rb
 - lib/schemad/abstract_handler.rb
+- lib/schemad/default_types.rb
 - lib/schemad/entity.rb
 - lib/schemad/extensions.rb
 - lib/schemad/normalizer.rb
@@ -104,7 +106,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.2
+rubygems_version: 2.4.5
 signing_key: 
 specification_version: 4
 summary: Simple schema DSL for services