configr 0.9.0 → 1.0.0

data/VERSION

@@ -1 +1 @@
-0.9.0
+1.0.0

data/configr.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{configr}
-  s.version = "0.9.0"
+  s.version = "1.0.0"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Josh Nesbitt"]
-  s.date = %q{2010-03-01}
+  s.date = %q{2010-08-05}
   s.description = %q{Configr aims to provide a clean interface to configuring and reading a set of configuration values. The idea evolved from using a standard hash as a configuration store into a more elegant way to declare and read values from within a hash. }
   s.email = %q{josh@josh-nesbitt.net}
   s.extra_rdoc_files = [
@@ -39,7 +39,7 @@ Gem::Specification.new do |s|
   s.homepage = %q{http://github.com/joshnesbitt/configr}
   s.rdoc_options = ["--charset=UTF-8"]
   s.require_paths = ["lib"]
-  s.rubygems_version = %q{1.3.5}
+  s.rubygems_version = %q{1.3.6}
   s.summary = %q{An elegant approach to creating and accessing configuration values.}
   s.test_files = [
     "spec/lib/configuration_block_spec.rb",

data/lib/configr/hash.rb

@@ -1,10 +1,15 @@
 module Configr
   module HashExtensions
+    
     def symbolize_keys!
+      _hash = {}
+      
       each do |k, v|
         self.delete(k.to_s)
-        self[k.to_sym] = v
+        _hash[k.to_sym] = v
       end
+      
+      self.merge! _hash
     end
     
     def recursive_symbolize_keys!
@@ -56,5 +61,4 @@ end
 
 class Hash
   include Configr::HashExtensions
-  
 end

data/readme.rdoc

@@ -101,7 +101,7 @@ Conceptually you could continue to nest configuration blocks as far as you wish.
 
 === Asserting key presence
 
-Sometimes when using configuration values you might want to assert whether the value exists before using it. Configr allows you to do this the #key_name? methods:
+Sometimes when using configuration values you might want to assert whether the value exists before using it. Configr allows you to do this with the #key_name? syntax:
   
   puts configuration.example_one? # => true
   puts configuration.doesnt_exist? # => false

metadata

@@ -1,7 +1,12 @@
 --- !ruby/object:Gem::Specification 
 name: configr
 version: !ruby/object:Gem::Version 
-  version: 0.9.0
+  prerelease: false
+  segments: 
+  - 1
+  - 0
+  - 0
+  version: 1.0.0
 platform: ruby
 authors: 
 - Josh Nesbitt
@@ -9,19 +14,23 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-03-01 00:00:00 +00:00
+date: 2010-08-05 00:00:00 +01:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: rspec
-  type: :development
-  version_requirement: 
-  version_requirements: !ruby/object:Gem::Requirement 
+  prerelease: false
+  requirement: &id001 !ruby/object:Gem::Requirement 
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
+        segments: 
+        - 1
+        - 2
+        - 9
         version: 1.2.9
-    version: 
+  type: :development
+  version_requirements: *id001
 description: "Configr aims to provide a clean interface to configuring and reading a set of configuration values. The idea evolved from using a standard hash as a configuration store into a more elegant way to declare and read values from within a hash. "
 email: josh@josh-nesbitt.net
 executables: []
@@ -63,18 +72,20 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      segments: 
+      - 0
       version: "0"
-  version: 
 required_rubygems_version: !ruby/object:Gem::Requirement 
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      segments: 
+      - 0
       version: "0"
-  version: 
 requirements: []
 
 rubyforge_project: 
-rubygems_version: 1.3.5
+rubygems_version: 1.3.6
 signing_key: 
 specification_version: 3
 summary: An elegant approach to creating and accessing configuration values.