configatron
configatron copied to clipboard
markbates
A super cool, simple, and feature rich configuration system for Ruby apps.
Configatron::Store#fetch with a falsey default should set and return that default. At the moment it sets and returns nil, for example: ``` configatron.configure_from_hash(test_config: {}) => {:test_config=>{}} configatron.test_config.fetch(:enabled, false) => nil...
Adding history entry so users can understand what is in the 4.5.1 release on rubygems.org. I don't think I can create a tag in github without ownership, but it would...
I'm guessing it's not thread safe? But I just want to confirm.
Fixed a couple of small warnings that appear when running Configatron with ruby 2.5 ``` lib/configatron/proc.rb:14: warning: instance variable @val not initialized DEPRECATED: Use assert_nil if expecting nil from /Users/kreynolds/Projects/configatron/test/functional/configatron.rb:162....
In our tests, we make use of rspec's before/after/around lifecycle hooks to set the state of the test, including configatron settings with `configatron.temp`. Unfortunately when you have multiple `configatron.temp` competing...
``` require 'configatron' => true 2.5.0 :002 > configatron.test = [] => [] 2.5.0 :003 > configatron.lock! => true 2.5.0 :004 > configatron.test [1] 2.5.0 :005 > configatron.test => [1]...
I love configatron, but although it solves a lot of things, it makes it rather difficult to work with unassigned keys. In a standard hash, or an `OpenStruct`, non existing...
It would be nice if `configatron.param?` will simply be (conceptually-) aliased to `!! configatron.param` ```ruby # Allow asking `configatron.something?` configatron.force = false p configatron.force ? "forced" : "not forced" p...
When you reference a variable that is not set with .include? it does not return false as you would expect, it returns "". ``` irb(main):009:0> x.ugh.include?(1) => ``` Considering it...
