are you able to reproduce it locally?

(def wrapped (mid/wrap-defaults #'simple-handler mid/api-defaults))
(def server (jetty/run-jetty simple-handler
                             {:port 3000
                              :join? false}))

{:headers
 {"accept" "*/*", "user-agent" "curl/7.79.1", "host" "localhost:3000"},
 :params {:foo "bar"}}

If you are seeing headers keywordized, look for any uses of ring.middleware.keyword-params in your project and see if you are pointing keyify-params at :headers somewhere

Yeah I tried that... I think the culprit will be aleph in the server where it's keywords. It seems that the header map reacts to both keys and strings? Knowing it wasn't the middleware I'll just adjust to using strings

https://github.com/clj-commons/aleph/blob/master/src/aleph/http/core.clj#L140

Yeah now I'm super confused. The server where the headers are keywords (and upper-case keywords at that!) I don't see any middleware or manual setting doing it...

check=> (get-in req [:headers "HOST"])
"localhost:3000"
check=> (get-in req [:headers :HOST])
"localhost:3000"
check=> (get-in req [:headers :HoSt])
"localhost:3000"

the headermap doesn't have those keys, its just the way it looks it up it calls (str/lower-case (name k)) on the lookup value

so all of these are looking for the header key "host"

Explains everything. Thanks a lot.

Read it carefully because it has an “added” map that can lookup as normal that can shadow the actual header map. Not sure how that’s used in aleph though

(defn text
  [ratom]
  [:input {:type "text"
           :default-value @ratom
           :on-change #(reset! ratom (.. % -target -value ))}])

(defn lister [ratom]
  [:ul
   (for [item @ratom]
     ^{:key item} [:li [text (r/atom item)]])]) ;; <-- this won't update


(defcard-rg text-card
  (fn [ratom _ ] [text ratom])
  (r/atom "edit me")
  {:inspect-data true}
  )
(defcard-rg lister-card
  (fn [ratom _] [lister ratom])
  (r/atom ["edit1" "edit2"])
  {:inspect-data true})

I think you need to pass a cursor down

https://reagent-project.github.io/docs/master/reagent.core.html#var-cursor

So don’t iterate on the dereferenced atom at the top level, iterate on (range (count @ratom)) and pass cursors for each index into each text component

thanks, cursor works, even wrap works. But i found them too heavy for changes the structure of one ratom to another, e.g. build atom of vector to atom of map and pass to child component. maybe that’s why most reagent tutorials i read use top level “global” state rather than passing triaged down atom-ish state to child components.

Why not just '(foo)? '(1 2 3) is the standard list literal https://www.clojure.org/guides/learn/syntax#_literal_collections

Because

(let [foo :foo] '(foo))  ;; => (foo)
(let [foo :foo] `(~foo)) ;; => (:foo)

Ah yeah. I can't think of a surprise or gotcha, but if I were reviewing the code I'd suggest just using (list :foo) as it's far more obvious what is going on.

It depends what you mean by list

The list function returns a list which is like a seq with extra stuff, syntax quote returns a seq

Good point. Exactly the type of detail I am asking about. In this case. I just need something appropriate as a second arg to cons, with values generally expected to be added/removed at the front.

cons will coerce a vector to a seq

If I output a vector, with the intention that it will be treated like a list, I am relying on the consumer, with no warning, to not do anything where vectors are treated differently.