I started a web project using scss… Is there a way to invoke sassc when the source files change? I really love live browser reloading, and running lein run every time my scss source files change is going to get old pretty fast.

Or is the standard workflow to develop using the .css file directly, then translate into scss files?

There doesn’t seem to be a cprop channel, so I figured this might be a good place to ask..

cprop’s readme states that For #3 (load-config) optionally takes a sequence of maps (via :merge) that will be merged after the defaults and in the specified sequence

But I’m not seeing the sequence being respected.

(:java-home (load-config :merge [(source/from-system-props) 
                                 (source/from-env)]))
read config from resource: "config.edn"
read config from file: ".lein-env"
=> "/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/"
(:java-home (load-config :merge [(source/from-env) 
                                 (source/from-system-props)]))
read config from resource: "config.edn"
read config from file: ".lein-env"
=> "/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/"
(:java-home (source/from-system-props))
=> "/Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home/jre”

Looks like I always end with the same :java-home in the result, no matter which order I pass the property maps on. I’d expect the second test to end in “/jre”.

That’s just a trivial example with a property that’s in both, but wondering why I’m seeing that behavior.

Hmm. Re-reading, it merges environment variables again after step 3, which is where the values from :merge come from. Given that… does it make sense to add (source/from-env) to the list used on :merge?