diff options
author | Serdar Sutay <serdar@opscode.com> | 2014-07-22 12:07:18 -0700 |
---|---|---|
committer | Serdar Sutay <serdar@opscode.com> | 2014-07-22 12:07:18 -0700 |
commit | da2f0ae30bf6d19f236ad7b0742a2b75e586fb8b (patch) | |
tree | a4064090c46052e88b3c4bb30673e990d1d4742c | |
parent | a038569070e9e59a7051594f9422c11e3adb7ab6 (diff) | |
parent | f2cbea4ea6442fbc1da2245daad34734754747ac (diff) | |
download | mixlib-config-da2f0ae30bf6d19f236ad7b0742a2b75e586fb8b.tar.gz |
Merge pull request #23 from mriddle/revert-22-master
Revert "Fix README typos"
-rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -112,9 +112,9 @@ Misspellings are a common configuration problem, and Mixlib::Config has an answ end ``` -Now if a user types `filename "~/output-mine.txt"` in their configuration file, it will toss an exception telling them that the option "filename" is unknown. If you do not set config_strict_mode, the filename option will be merrily set and the application just won't know about it. +Now if a user types `fielname "~/output-mine.txt"` in their configuration file, it will toss an exception telling them that the option "fielname" is unknown. If you do not set config_strict_mode, the fielname option will be merrily set and the application just won't know about it. -Different config_contexts can have different strict modes; but they inherit the strict mode of their parent if you don't explicitly set it. So setting it once at the top level is sufficient. In the above example, `logging.base_name 'mylog'` will raise an error. +Different config_contexts can have different strict modes; but they inherit the strict mode of their parent if you don't explicitly set it. So setting it once at the top level is sufficient. In the above example, `logging.base_naem 'mylog'` will raise an error. In conclusion: *always set config_strict_mode to true*. You know you want to. |