lein-figwheel 2017-06-21

If I’m in a namespace and I set up an alias for dev purposes, like

(require '[cljs.spec.test.alpha :as st])

so that I can do

(st/check `my-fn)

if I change and save my file, it blows away the st alias. I’ve added ^:figwheel-no-load to my ns form, which does indeed cause it to not automatically load changes to my code, but it still removes the alias. Has anyone solved this one, short of putting the dev-time namespace and alias directly in my ns form?

bhauman17:06:07

@mfikes that's interesting, I'm not familiar with the mechanism behind require aliasing, I thought it was just a compiler state thing. Ahhhhh ... the file gets compiled ... so it changes the compiler state and thus the alias is gone.

bhauman17:06:24

So in terms of a solution how about a tooling namespace that you reuse???

mfikes17:06:35

@bhauman When you do a require in a REPL, and it has an alias, it essentially adds that alias to whatever aliases you might already have.

bhauman17:06:37

(tl/check)

bhauman17:06:53

gotcha 🙂

mfikes17:06:59

It is no big deal to come up with a clean solution to this use case. Perhaps it might become more commonly used with Spec adoption.

bhauman17:06:04

yeah so there is definitely a problem with doing repl driven versus save driven development here