My personal opinion is to prefer keywords, and prefer less preprocessing of the configuration before the program uses it.
If it gets to a place where the configuration changes a lot, and a "natural" (read: clojure-like) expression of the configuration in EDN has either a lot of redundancy, or bits that must agree with each other, then I'd look to create a sublanguage for the config that makes it harder to specify incorrect things, and that's when I might use symbols. That depends on how the language looks, mostly. That said, I have a place in my config where I use symbols as map keys because it is specifying GraphQL attribute names, and other non-Clojure developers edit it. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/CAB6_SoanVGAW2jhZNY0NS9XFGap6q5r7HHSgsRN99EoZ2ehCDw%40mail.gmail.com.
