README.md in configatron-4.0.2 vs README.md in configatron-4.0.3
- old
+ new
@@ -1,11 +1,11 @@
# Configatron
[](https://travis-ci.org/markbates/configatron) [](https://codeclimate.com/github/markbates/configatron)
Configatron makes configuring your applications and scripts incredibly easy. No longer is a there a need to use constants or global variables. Now you can use a simple and painless system to configure your life. And, because it's all Ruby, you can do any crazy thing you would like to!
-One of the more important changes to V3 is that it now resembles more a `Hash` style interface. You can use `[]`, `fetch`, `each`, etc...
+One of the more important changes to V3 is that it now resembles more a `Hash` style interface. You can use `[]`, `fetch`, `each`, etc... Actually the hash notation is more robust since the dot notation won't work for some property names. See section "Differences between dot and hash notation" for more details.
## Installation
Add this line to your application's Gemfile:
@@ -73,9 +73,15 @@
configatron.email.pop.address # => 'pop.example.com'
configatron.email.pop.port # => 110
# and so on...
```
+
+### Method vs hash access
+
+As a note, method (`configatron.foo`) access will be shadowed by methods defined on the configatron object. (The configatron object descends from [`BasicObject`](http://apidock.com/ruby/BasicObject) and includes `Kernel`, so it should have a pretty bare set of methods.)
+
+If you need to use keys that are themselves method names, you can just use hash access (`configatron['foo']`).
### Namespaces
The question that should be on your lips is what I need to have namespaced configuration parameters. It's easy! Configatron allows you to create namespaces.