From e0b21871a628438a26fcfad7e0e4bece23f3ee7a Mon Sep 17 00:00:00 2001 From: gered Date: Sat, 14 Jun 2014 17:42:55 -0400 Subject: [PATCH] let's be honest -- the most common scenario is for this to be turned on --- src/clj_jtwig/options.clj | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/src/clj_jtwig/options.clj b/src/clj_jtwig/options.clj index 4bd7496..6d20e15 100644 --- a/src/clj_jtwig/options.clj +++ b/src/clj_jtwig/options.clj @@ -33,9 +33,4 @@ ; whether or not to automatically stringify the keys of model-maps. Jtwig requires that all ; the keys will be strings for model value resolution to work correctly. if you are already ; setting your keys as maps, then you can turn this option off to save a bit on performance - ; NOTE: why use false as a default? less "magic" out of the box. most people when first - ; using this library will probably run into this issue and then want to turn this - ; option on, but i think that's preferable (forcing the user to learn about this) - ; then later on wondering why the value from the model passed to a custom jtwig - ; function has strings for keys instead of keywords, etc... - :stringify-keys false})) \ No newline at end of file + :stringify-keys true})) \ No newline at end of file