hold 1.0.1 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 6eb66a9b993a58327effef42e2503297ab0fdad6
-  data.tar.gz: 205a84af71021efa70c74995dc8ae0c3bd904e25
+  metadata.gz: ccf3c450bd0581651f077eba61da713f1d1d2c55
+  data.tar.gz: 9c91f6779ba78610c0cbf5140f1c401994b04f6a
 SHA512:
-  metadata.gz: 61fb6def62557bfb2ecfd68c0531f9f70a3b4f2ccacb4a0581862c8edf7c1e2cee1279a2a747760b5bda18e3668ff28996debfcd99a3e5ecbb65577b167ffdf7
-  data.tar.gz: c7571b92d84ff5ae33744636e7326e639674b52e550dcebc6e87337d7e704d43c3bf53d794fa64d8cf9ee19fbcff2dddc27ec7b44ecdf96cfbe8620d4aed2242
+  metadata.gz: a9264703012fd325bf2dacd390aa732830dbb6874c2da1cf05a774a15a8424ff300f46c268a6351f983cd9af29a79ccf8851407c8e358dab3b27f4eb74322dc3
+  data.tar.gz: fbf1e4cb8abfd62aad061b5e5675f251e30e2a6d357c8da5e31c021a56d9624c6eeecdf2bf47976512d815fba8f458a1fe67684eefd1c1ea4fa2303a1acad52d

data/README.md

@@ -1,4 +1,5 @@
-![Build Status](https://travis-ci.org/mediasp/hold.svg?branch=master)
+[![Build Status](https://travis-ci.org/mediasp/hold.svg?branch=master)](https://travis-ci.org/mediasp/hold)
+[![Gem Version](https://badge.fury.io/rb/hold.svg)](http://badge.fury.io/rb/hold)
 # Hold
 
 A ruby library geared towards separating persistence concerns from data model classes.

data/lib/hold/serialized.rb

@@ -86,10 +86,13 @@ module Hold
 
     def get_by_id(id)
       json = @cache.get_with_key(cache_key(id))
-      string_hash = @serializer.deserialize(json)
-      string_hash = string_hash.inject({}){|memo,(k,v)|
-        memo[k.to_sym] = v; memo
-      }
+      if json
+        string_hash = @serializer.deserialize(json)
+        string_hash.inject({}) do |memo, (k,v)|
+          memo[k.to_sym] = v
+          memo
+        end
+      end
     end
 
     def delete_id(id)
@@ -99,6 +102,5 @@ module Hold
     def contains_id?(id)
       @cache.has_key?(cache_key(id))
     end
-
   end
 end

data/lib/hold/version.rb

@@ -1,3 +1,3 @@
 module Hold
-  VERSION = '1.0.1'
+  VERSION = '1.0.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: hold
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.2
 platform: ruby
 authors:
 - Matthew Willson
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-05-16 00:00:00.000000000 Z
+date: 2014-12-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -140,20 +140,6 @@ dependencies:
 description: |2
     A persistence library based more closely on the repository model.
     Used in production for several years.
-
-    To summarize, the idea is that
-
-    * You have Repositories which are responsible for persisting objects in a data store
-    * Your data objects know nothing about persistence. They are just 'plain old' in-memory ruby objects can be created and manipulated independently of any particular repository.
-
-    This is a substantially different approach to the widely used ActiveRecord pattern.
-
-    Of course there are various trade-offs involved when choosing between these two approaches. ActiveRecord is a more lightweight approach which is often preferred for small-to-mid-sized database-backed web applications where the data model is tightly coupled to a database schema; whereas Repositories start to show benefits when it comes to, e.g.:
-
-    * Separation of concerns in a larger system; avoiding bloated model classes with too many responsibilities
-    * Ease of switching between alternative back-end data stores, e.g. database-backed vs persisted-in-a-config-file vs persisted in-memory. In particular, this can help avoid database dependencies when testing
-    * Systems which persist objects in multiple data stores -- e.g. in a relational database, serialized in a key-value cache, serialized in config files, ...
-    * Decoupling the structure of your data model from the schema of the data store used to persist it
 email:
 - mark@mediasp.com
 - tom@mediasp.com