Is it ok to have a clj/app/config.clj file and a cljs/app/config.cljs file, both of which start with (ns app.config …? Will Clojure and ClojureScript know that these are totally unrelated or will the functions in the two files live in the same namespace and cause problems?

@fasiha: Ignoring macros for now, you will have no issues with having two files with the same ns, one with .clj and one with .cljs. The Clojure reader looks for it’s ‘native’ extension first (`.clj`, .cljs), then to cljc if it can’t find it.

There is no way (that I know of) for Clojure or ClojureScript to have functions in both files’s loaded at the same time

Thanks @danielcompton! Clojure just makes life easy

what book do you recommend for clojurescript in general

@lewix: I don't have a direct answer, but I'll describe what I did because I had a rough experience with googling "clojurescript tutorial". I went through @bhauman's https://github.com/bhauman/lein-figwheel/wiki/Quick-Start, then went through several React.js JavaScript tutorials and porting them to ClojureScript/sablono. Plus a lot of googling for various things as they came up… probably not the most time-efficient method 😕

@fasiha: I'm already familiar with react/redux. I'll try fighwheel thanks

what is the recommended way of making reagent components that take optional parameters with default values? aka defaultProps in react

@bojan.matic Not that I know of; I have rolled my own thing for this.

https://gist.github.com/anonymous/2ab4b4adedc1c35881a96b8871e9f7ab

(I try not to write too many macros but I found myself writing stuff for default arguments over and over again)

perhaps i misspoke, i didn’t mean optional as much as i meant default - so, parameters that always need to be provided but you can set a sensible default and skip it most of the time

how do you use this macro?

Well... your thing is easier

(defn foo-component [{:keys [:awesome? :style] 
                      :or {:awesome? true, :style {:overflow "scroll"}}
                      :as params}] 
; Code goes here
)

That will set awesome? to true by default, and create a default style (but you should really use CSS, this is bad practice)

My thing is basically the same instead you write defnp instead of defn, and when you are actually writing your hiccup out you can write [foo-component] and it behaves the same as [foo-component {}]

oh, i see

thanks

i saw {:keys} a few times in examples, but never knew how it really works…does it set missing keys to nil? I see it described as a “directive”, what’s a directive?

Yeah, it sets the missing keys to nil

A directive is a special form in a destructuring binding involving maps

http://clojure.org/reference/special_forms

The other directives are :strs and :syms but I've honestly never used those nor seen them used

Is there a way to force a clojurescript file to be recompiled when a macro it uses changed? The macro is in another jar.

alpheus: are you using checkouts?

no, I don't know what checkouts means

sorry, it’s a lein thing

I'm installing the jar that defines the macro in a private repo

ah, yeah

checkouts can help with that

if you put a symlink to that other project in checkouts

lein will automatically include its source paths

and you can add that path to your :source-paths in cljsbuild

(assuming those are the tools you use)

I’m doing this right now with a project I’m working on

https://github.com/tel/oak-todomvc

Yes, using lein. Does a version ending in "-SNAPSHOT" mean the dependency always gets a fresh copy from the repo?

I believe so, yes

checkouts accelerates this even more, though, since it means you won’t even need to reload things like repls or figwheel or autobuilders

Checkouts means I need the source of both projects on my local machine (for the symbolic links). That may be a problem for my configuration.

yes, that is true

Maybe removing the corresponding .js file is enough to force a recompilation?

hm, not sure

what do you guys use to log things that happen on the client? one solution would be an HTTP endpoint that appends to a flat file. is there any reason to go more advanced than that?

now that I think about it, I might as well put the logs in a DB

has anyone found a good way to get third-party library css into your clojurescript bundle?

@lwhorton: by bundle do you mean some compilation target directory?

because if so, I’ll use http://webjars.org + boot with something like this (sift :add-jar {'org.webjars/font-awesome #"css/.+\.css$”}) to add the file to my bundle

I only know how to pull files out of jars in Boot, I can’t help you with Lein.

thanks for that @adamfrey ill take a look. I’m considering a crazy pipeline of stylus -> css-modules -> css -> trimmed via csso -> clojurescript module

i think the hardest part would just be something that can convert json + css into a clojurescript namespace/module exposing the proper symbols… and perhaps a runtime for loading/reloading