recursive_case_indifferent_ostruct 0.1 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b398b7f98e4169257f4811888715dd82fd43b4b2
-  data.tar.gz: f44fee346580aec8bc67449f40223967852f3bc6
+  metadata.gz: f29ef3fcb8655257fc1562d6bf09f61be465b3a9
+  data.tar.gz: 46487154c944ea8af316dfad6db57ec28f5fe82f
 SHA512:
-  metadata.gz: e23e8daeca037f194a719201a486c509462c0e0abaa5bb52f8eb8e392075e885b96e2229195860b1bfc63338ff44202124cab26d8cc2d232bb4f1255cca5c399
-  data.tar.gz: fde5b277fe47328995e2f6d762f2ea14c11ed1bb41f1b63566807b032541d16673c454737140c1a088773397b527bccf98c65b764aa54221882f5a28433ddc7e
+  metadata.gz: 86b4fc3a58b06dbc6b663b95180af5cba20c0db15f10d74659cc081ce3a2edcd7fff9267c8aa587287bfb53669ff883c9293e6d229b21b89b99424d3f876f416
+  data.tar.gz: 8fa6ec8cb3e36ff33cd60e8b78096f559a55738ead20cbeb74b4f26a5b454a564983e8e2bb9f3e9643ab05caf83d8446171c3235da6b7500073f2ed0b76c893d

data/README.md

@@ -36,7 +36,7 @@ user.last_name # "Johnson"
 user.father.age # 72
 user.siblings[0].age # 12
 
-user.birth_place    = "New York" # set fields
+user.birth_place    = "New York" # sets Birth-Place
 user.first_name     = "Ken" # sets {"firstName" => "Ken", "first-name" => "Ken"}
 user.mothers_maiden = "Woods" # Since case is mixed in that hash, use default :lower_camel
 
@@ -44,7 +44,7 @@ user.mothers_maiden = "Woods" # Since case is mixed in that hash, use default :l
 user.to_h
 # {
 #   "firstName"   => "Ken",
-#   "first-name"  => "Bobby",
+#   "first-name"  => "Ken",
 #   "LAST_NAME"   => "Johnson",
 #   "Birth-Place" => "New York",
 #   "father"      => {
@@ -58,6 +58,18 @@ user.to_h
 ```
 
 
+```
+# .merge() is case insensative
+user = RecursiveCaseIndifferentOstruct.new(first_name: "Bob")
+new_user = user.merge({"FirstName" => "Bobby"})
+new_user.first_name # Bobby
+user.first_name # Bob
+
+user.merge!({"FirstName" => "Bobby"})
+user.first_name # Bobby
+
+```
+
 ### Case Matching
 Since the key matching is fuzzy, should there be two attributes with
 the same name but different case (`first-name` and `firstName`), the
@@ -89,6 +101,7 @@ The value can still be accessed via `json.pi_value`.
 if the method is not defined and there is not attribute matching that
 name. However, all the hash methods operate on the original hash, so
 `#has_key?`, `#each`, `#fetch`, etc, will not be case-indifferent.
+Feel free to implement them and submit a PR.
 
 ```ruby
 json = RecursiveCaseIndifferentOstruct.new({

data/lib/recursive_case_indifferent_ostruct.rb

@@ -19,6 +19,20 @@ class RecursiveCaseIndifferentOstruct
   def []=(key, value)
     handle_assignment(key, value, true)
   end
+
+  def merge(other_hash)
+    out = self.dup
+    other_hash.each do |k, v|
+      out.send("#{k}=", v)
+    end
+    out
+  end
+  
+  def merge!(other_hash)
+    other_hash.each do |k, v|
+      send("#{k}=", v)
+    end
+  end
   
   def method_missing(method_sym, *args, &block)
     method_name   = method_sym.to_s

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: recursive_case_indifferent_ostruct
 version: !ruby/object:Gem::Version
-  version: '0.1'
+  version: 0.1.1
 platform: ruby
 authors:
 - Tyler Roberts
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-12-15 00:00:00.000000000 Z
+date: 2016-03-23 00:00:00.000000000 Z
 dependencies: []
 description: See github.
 email: code@polar-concepts.com
@@ -38,7 +38,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.5
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: Access JSON or Hashes attributes without regards to snake_case, camelCase,