It sounds to me like you may be thinking about this backwards. You don’t
necessarily want to (enable-console-print!) *any* time that code is run,
just when you’re running your entire app. Rather than require that code
from each of your files, I’d suggest putting it at the top of (or requiring
it
It’s very cumbersome to add (:require [init]) manually to each file.
Is there another solution?
—
Sent from Mailbox
On Mon, Nov 10, 2014 at 4:43 PM, Thomas Heller th.hel...@gmail.com
wrote:
That SHOULD be handled via the dependency graph of your namespaces, that
means if one namespace
Yes, but I would recommend using the require. It is much cleaner from the
dependency graph perspective and tooling can support you way better. Also it is
not that much work, maybe a couple seconds. I also tend to have a util
namespace with general helper functions which is a good fit for the
That SHOULD be handled via the dependency graph of your namespaces, that means
if one namespace requires code from another to be loaded it should list it in
its (:require ...) declaration. This way you ensure that it was loaded in the
right order.
init.cljs:
(ns init)
(enable-console-print!)
