collector 0.1.1 → 0.1.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 1f67cd923c0bfdec2effecea4b750ba9b3f7ba8a
+  data.tar.gz: 94cd9b47c2060bd13ffd3325775324c1d4d461dd
+SHA512:
+  metadata.gz: cb4e10a1276cf3e249f253ddbdcd625c83bac8ca57cc5b9d1f8b59d3c9a4fc3645566dd20927ee30dfb6a5519a6314e11f688868b93cd56d166df3d7ee26c945
+  data.tar.gz: ff6096b388a902c66c9475458781678bc3ff457548ec4b6f0ee5e20e3bd56326c6556e1ded1cdb84214e11f5ac34bcaec00748473ca399a2d2a83c5e9b685c2d

data/README.md

@@ -1,7 +1,7 @@
 # Collector
 
 [![Build Status](https://travis-ci.org/brandonweiss/collector.png)](https://travis-ci.org/brandonweiss/collector)
-[![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/brandonweiss/collector)
+[![Code Climate](https://codeclimate.com/github/brandonweiss/collector.png)](https://codeclimate.com/github/brandonweiss/collector)
 
 Collector is an implementation of the Repository Pattern for MongoDB. For those new to the Repository Pattern, it is a Facade that isolates the persistence layer from your application. If you're familiar with Rails, or more specifically ActiveRecord or most other ORMs, you'll know that the models and persistence layer are tightly coupled—literally they are the same object. That pattern is a great way to cut your teeth, but ultimately it's a terrible design. Your application does not and should not care about how its data is persisted. Collector will help with that.
 
@@ -106,7 +106,7 @@ Currently only MongoDB. I'd like to add an in-memory store, and if possible, a f
 
 If you don't already know why you need or want the Repository Pattern, then don't use it yet. It took me far longer than it should have to realize the benefits, despite having them explained to me many times. I just never really understood them until I'd actually experienced the pain this pattern solves myself. Once you do, come back and try it out.
 
-### This looks awfully similar to [curator](http://github.com/braintreee/curator). What's the difference?
+### This looks awfully similar to [curator](http://github.com/braintree/curator). What's the difference?
 
 I rolled my own application-specific version of the Repository Pattern for each project I worked on before I realized I was using it often enough to merit extracting it into a gem. Right about that time Braintree announced curator, and since both their implentation and mine were very similar—except theirs was further along and had more features—I decided to use theirs instead. But after using it for a few months and then reading through the code to try and contribute back to it, I decided to go back to my own implementation and extract it into a gem after all.
 

data/collector.gemspec

@@ -18,6 +18,6 @@ Gem::Specification.new do |gem|
   gem.require_paths = ["lib"]
 
   gem.add_dependency "activesupport", "~> 3.2.8"
-  gem.add_dependency "mongo",         "~> 1.8.0"
-  gem.add_dependency "bson",          "~> 1.8.0"
+  gem.add_dependency "mongo",         "~> 1.9.0"
+  gem.add_dependency "bson",          "~> 1.9.0"
 end

data/lib/collector/version.rb

@@ -1,3 +1,3 @@
 module Collector
-  VERSION = "0.1.1"
+  VERSION = "0.1.2"
 end

metadata

@@ -1,20 +1,18 @@
 --- !ruby/object:Gem::Specification
 name: collector
 version: !ruby/object:Gem::Version
-  version: 0.1.1
-  prerelease: 
+  version: 0.1.2
 platform: ruby
 authors:
 - Brandon Weiss
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-01-29 00:00:00.000000000 Z
+date: 2013-06-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -22,7 +20,6 @@ dependencies:
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -30,35 +27,31 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: mongo
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 1.8.0
+        version: 1.9.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 1.8.0
+        version: 1.9.0
 - !ruby/object:Gem::Dependency
   name: bson
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 1.8.0
+        version: 1.9.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 1.8.0
+        version: 1.9.0
 description: An implementation of the Repository Pattern for MongoDB.
 email:
 - brandon@anti-pattern.com
@@ -83,27 +76,26 @@ files:
 - test/test_helper.rb
 homepage: ''
 licenses: []
+metadata: {}
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.23
+rubygems_version: 2.0.0
 signing_key: 
-specification_version: 3
+specification_version: 4
 summary: An implementation of the Repository Pattern for MongoDB
 test_files:
 - test/collector/model_spec.rb