nxt_config 0.2.1 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3d8967fb731cfbb8388f8f72b4111137b1a65f59e597982d43e86f9da0280d89
-  data.tar.gz: b111ac2f900a61e4361c0475fb9cc2d85a55e12a78764b5fef04baf948d06821
+  metadata.gz: 0eeb33c443f139f43cbf12e64594e24a7623329461dc767d5fa5d98a34cc1606
+  data.tar.gz: d707cd6e76a1ca3cd283420ebe2d54bd2ade462d069fb84ecac31484c63f7c08
 SHA512:
-  metadata.gz: 9cc788737cce9c3addc730d6f6999b536b1d9cd2fe0d53a3c75f6ced49e3195fc622300486ee70c6942385c6b16971e08615858c8ab6c8abaa0312a7c410321a
-  data.tar.gz: 2e44b14680acb33d9bb9585dc563d8536ddf131842b66963e8e3a6fe6c4227a9c8a48a1206f68fd857ca6ca9a7d3864629e269bb7758939496a965144d8fdac8
+  metadata.gz: 6552d0798f6c99f14fa4dc5f453091d5bba323759d20fbbac9a05b34a1cadce2eb65b10fcf53ef9b1a3e8ad095d8c198417794d02e7ebd832ad7ff1fdb4d2c50
+  data.tar.gz: 621f00981928f7d1a7e912274af295d7d5cf6c4613987068ef6b8fa850418719e651f0055c4c7e0b09c9bff4314918fc6b5156cae574484e8d537ca9cb57319e

data/CHANGELOG.md

@@ -1,3 +1,12 @@
+# v0.2.2 2019-03-10
+
+### Added
+
+- [internal] Allow to load NxtConfig from a hash source
+
+[Compare v0.2.1...v0.2.2](https://github.com/nxt-insurance/nxt_config/compare/v0.2.0...v0.2.1)
+
+
 # v0.2.1 2019-01-11
 
 ### Added

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    nxt_config (0.2.1)
+    nxt_config (0.2.2)
 
 GEM
   remote: https://rubygems.org/

data/README.md

@@ -27,7 +27,8 @@ Or install it yourself as:
 
 ## Usage
 
-You can load YAML files and populate their content into a configuration object using `NxtConfig.load`. If you are in a rails application, you can do this in an initializer (e.g. `config/initializers/nxt_config.rb`).
+You can create a configuration object using `NxtConfig.load` from YAML files or directly from a hash. 
+If you are in a rails application, you can do this in an initializer (e.g. `config/initializers/nxt_config.rb`).
 
 ```ruby
 module MyRailsApp
@@ -35,7 +36,9 @@ module MyRailsApp
 end
 ```
 
-Of course you can also load configuration structs everywhere else in the application. Depending on where you assign it to a constant, you can have many configuration structs available via constants namespaced all over your application, scoped to the context where you need them.
+Of course you can also load configuration structs everywhere else in the application. 
+Depending on where you assign it to a constant, you can have many configuration structs available via constants namespaced all over your application, 
+scoped to the context where you need them.
 
 ```ruby
 # Use struct like method chaining to access nested data

data/lib/nxt_config.rb

@@ -5,8 +5,13 @@ require "nxt_config/struct"
 require "nxt_config/version"
 
 module NxtConfig
-  def load(filename)
-    source_hash = YAML.safe_load(ERB.new(File.read(filename)).result)
+  def load(filename_or_hash)
+    if filename_or_hash.respond_to?(:to_h)
+      source_hash = filename_or_hash
+    else
+      source_hash = YAML.safe_load(ERB.new(File.read(filename_or_hash)).result)
+    end
+
     Struct.new(source_hash)
   end
 

data/lib/nxt_config/version.rb

@@ -1,3 +1,3 @@
 module NxtConfig
-  VERSION = "0.2.1".freeze
+  VERSION = "0.2.2".freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: nxt_config
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.2
 platform: ruby
 authors:
 - Nils Sommer
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-01-11 00:00:00.000000000 Z
+date: 2020-03-10 00:00:00.000000000 Z
 dependencies: []
 description: Create namespaced, immutable objects serving configuration properties
   to your ruby application.