does anyone know if weavejester/hiccup has something similar to re-agent’s [:<>]? I know it’s not a react lib (there’s no concept of fragments), but I have cases like this:

(def content
  [:div  ;; <- I am forced to wrap it in a div, otherwise hiccup complains
    [:li "one"]
    [:li "two"]
    [:li "three"]])

(html5 
  [:ul content])

I can of course do it this way:

(def content [[:li "one"] [:li "two"] [:li "three"]])

  (html5 [:ul (map identity content)])

I have an issue with figwheel-main, but #figwheel-main has considerably less users than this one. I am therefore reposting my question here: I am getting a lot of unwanted log information after I start my figwheel application. It seems to comes from the underlying figwheel http server. The log level is huge and I'm not interested in any of it. The origin namespace is `org.eclipse.jetty`

in re-frame parlance, would an on-change event on an input that causes things to be drawn on a canvas on the page be best achieved by https://github.com/day8/re-frame/blob/master/docs/Effects.md?

on-change –> dispatch –> event –> effect –> draw?

what does clojurescript development look like without figwheel or shadow? anyone have a representative repo somewhere? Wondering where compiler options and build is put. and repl environment look like

it goes into the deps.edn, right? https://github.com/clojure/clojurescript/blob/master/deps.edn https://clojurescript.org/guides/quick-start

@dpsutton if you're using ClojureScript directly you're probably using cljs.main you can supply build options in edn files

if you've used figwheel-main it's really not that different, figwheel-main is modeled on cljs.main

FWIW, for web I use figwheel-main because it just does a bunch of nice things that the standard browser REPL doesn't

i'm looking at build.api and then throwing that into webpack. just learning all the raw tools so i understand how they can/should compose

for Node.js I don't use anything - cljs.main is sufficient

build.api is useful, but I rarely use it now cljs.main can do nearly all typical tasks, and deps.edn aliases can make typical commands quite short

you don't use nrepl/piggieback i take it? static analysis in cursive and raw terminal there?

at some point I'd like to make the standard broswer REPL a bit more capable - but the existence of Figwheel just makes that a low priority - about the only time browser REPL gets worked on is if we're updating the docs so beginners and I see an area for improvement if you just want get the basic idea

I haven't used nrepl / piggieback for many, many years - no offense but I found that stuff to fragile and opaque many years ago

i understand

cljs.main works just like clojure.main - stdio works pretty much everywhere

that + Emacs inf-clojure, and Cursive have worked great for me and when things go wrong there's nothing in between me and the failure

yes that aspect is very nice.

one thing that's not quite been very clear is that cljs.main has been extensible for a quite some time - there were a couple of issues but I just fixed most of those and they'll be in the next release

at some point I'd like to document that for would be tool builders

it's pretty easy to write a custom build tool in a couple of hundred lines and you can literally reuse all of cljs.main + your extensions

and end up with something that anybody that knows cljs.main can pick up very quickly.

My hesistation has been towards the use of npm deps. And it sounds like that objection will be going away soon

Anyone know how to access HTML elements in cljs and set their inline style dynamically?

Trying to do something like this but in cljs

(.-style (first (array-seq (.getElementsByClassName js/document "vector-bar"))))

This is how I’m trying to get at it

But all I’m seeing is this as a response

#object[CSSStyleDeclaration [object CSSStyleDeclaration]]

Any way to change the CSS inside the style map through cljs js interop or am I stuck?

(set! (. el -style -backgroundColor) "red")