gered/clj-jtwig
Archived
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

let's be honest -- the most common scenario is for this to be turned on

Browse source
This commit is contained in:
Gered 2014-06-14 17:42:55 -04:00
parent da0097a100
commit e0b21871a6
1 changed files with 1 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
src/clj_jtwig/options.clj
View file

@ -33,9 +33,4 @@
; whether or not to automatically stringify the keys of model-maps. Jtwig requires that all ; 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 ; 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 ; 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 :stringify-keys true}))
; 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}))