README.md in anyway_config-2.5.1 vs README.md in anyway_config-2.5.2
- old
+ new
@@ -1,8 +1,9 @@
[](https://cultofmartians.com/tasks/anyway-config-options-parse.html#task)
[](https://rubygems.org/gems/anyway_config) [](https://github.com/palkan/anyway_config/actions)
[](https://github.com/palkan/anyway_config/actions)
+[](https://github.com/palkan/anyway_config/actions)
# Anyway Config
> One configuration to rule all data sources
@@ -612,17 +613,17 @@
Environmental variables for your config should start with your config name, upper-cased.
For example, if your config name is "mycoolgem", then the env var "MYCOOLGEM_PASSWORD" is used as `config.password`.
-By default, environment variables are automatically type cast\*:
+By default, environment variables are automatically type cast (rules are case-insensitive):
-- `"True"`, `"t"` and `"yes"` to `true`;
-- `"False"`, `"f"` and `"no"` to `false`;
+- `"true"`, `"t"`, `"yes"` and `"y"` to `true`;
+- `"false"`, `"f"`, `"no"` and `"n"` to `false`;
- `"nil"` and `"null"` to `nil` (do you really need it?);
-- `"123"` to 123 and `"3.14"` to 3.14.
+- `"123"` to `123` and `"3.14"` to `3.14`.
-\* See below for coercion customization.
+Type coercion can be [customized or disabled](#type-coercion).
*Anyway Config* supports nested (_hashed_) env variables—just separate keys with double-underscore.
For example, "MYCOOLGEM_OPTIONS__VERBOSE" is parsed as `config.options["verbose"]`.