Fork me on GitHub
#clojurescript
<
2020-12-18
>
Jack Arrington00:12:40

Just want to say, I really appreciate that the docs at http://cljs.github.io/api/ include the source code right at the bottom of each page. Makes finding the "ground truth" much easier and has gotten me way more comfortable with the language in general 🎉.

3
Jon03:12:59

is this a bug?

jaide04:12:59

How does one print an html entity with reagent again?

jaide14:08:39

Hah I was reading that the other day. Glad it's documented now! Couldn't quite figure out how to do it from node instead of the browser though, ended up just using the character itself

jaide04:12:34

Nevermind, found the docs 😅

Timofey Sitnikov11:12:29

Good Morning Clojurians, I super confused. Why does shadow-cljs start the development http server when watching main build even if the :dev-http entry is in the :test build? Looking at the https://github.com/fulcrologic/fulcro-rad-demo/blob/master/shadow-cljs.edn, under :builds -> :test -> :devtools it calls for shadow-cljs back-end server to start. I have been assuming that it will only start for the test build, but when I start the main build, I still get the http server:

[I] /home/sporty/clojure/fulcro/fulcro-rad-demo-sittim~> shadow-cljs watch main
shadow-cljs - config: /home/sporty/clojure/fulcro/fulcro-rad-demo-sittim/shadow-cljs.edn
shadow-cljs - starting via "clojure"
shadow-cljs - HTTP server available at 
shadow-cljs - server version: 2.11.8 running at 
shadow-cljs - nREPL server started on port 9000
shadow-cljs - watching build :main
[:main] Configuring build.
[:main] Compiling ...
GUARDRAILS IS ENABLED. RUNTIME PERFORMANCE WILL BE AFFECTED.
Guardrails was enabled because the CLJS Compiler config enabled it
[:main] Build completed. (928 files, 0 compiled, 0 warnings, 18.48s)
If I comment out the :devtools section in the :test build, it does not start the server. Why does it start the server.

thheller11:12:46

@timofey.sitnikov dev-http is always started and not tied to any specific build in general. the new [dev-http](https://shadow-cljs.github.io/docs/UsersGuide.html#dev-http) docs make that a bit clearer. it can be useful to have that server to quickly test release builds and so on

6
Timofey Sitnikov11:12:12

OK, but that looks like the :dev-http config entry is not in the right place? It makes it look like it is particular to the test build. Is that correct?

Timofey Sitnikov11:12:28

One more question, If I spin up my own back end server, will having shadow-cljs server conflict with anything?

Michaël Salihi14:12:04

@timofey.sitnikov No conlict, just be careful to take a different port.

3