purple_hash 1.0.0 → 1.0.1

data/CHANGELOG

@@ -0,0 +1,5 @@
+# 1.0.1
+ * Added (optional) core extension for `Hash#to_purple_hash
+
+# 1.0.0
+ * First release

data/README.md

@@ -16,23 +16,16 @@ config # => {:db => {:user => 'root'}}
 ```
 
 Because a `PurpleHash` is simply a sub-class of `Hash` you can do anything you
-would normally be able to without any hacks or tricks. Though not provided by
-this library, you could extend `Hash` to provide a `#to_purple_hash` like so:
-
-```ruby
-class Hash
-  def to_purple_hash
-    PurpleHash.new(self)
-  end
-end
-```
+would normally be able to without any hacks or tricks. A core extension of Hash
+is provided if you wish to use it, simply require `core_ext/hash/purple_hash`
+and call `#to_purple_hash` on any Ruby hash to get a `PurpleHash` back.
 
 **Note:** If you try to change the default value on a `PurpleHash` a `RuntimeError`
 will be raised informing you that this is not allowed.
 
 ## API
 
-PurpleHash provides a very basic API on top of what Hash already provides.
+`PurpleHash` provides a very basic API on top of what Hash already provides.
 
 ### `#configure_from_hash(hash)`
 

data/Rakefile

@@ -2,8 +2,8 @@ require 'rubygems'
 require 'bundler/setup'
 require 'rspec/core/rake_task'
 
-desc 'Run Gesch unit tests.'
+desc 'Run purple_hash unit tests.'
 task default: :spec
 
-desc 'Run Gesch unit tests.'
+desc 'Run purple_hash unit tests.'
 RSpec::Core::RakeTask.new

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: purple_hash
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-03-25 00:00:00.000000000 Z
+date: 2012-05-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -69,6 +69,7 @@ files:
 - Gemfile.lock
 - lib/purple_hash.rb
 - LICENSE
+- CHANGELOG
 - Rakefile
 - README.md
 - spec/purple_hash_spec.rb