Fork me on GitHub

@mikethompson I ended up with a bit of a frankenstein solution, where I do

{:component-did-update ;;TODO this causes way too many calls to .focus, wonder if I can reduce this with a different lifecycle hook?
            (fn [this]
(.focus (r/dom-node this)))


My problem is that the input component to be focused is "rendered" when the app is rendered, it's just not visible until later (when its popup has opened) and by then, the user has of course moved the focus elsewhere. Therefore, :auto-focus seemed less viable. But then, there is nothing deterring me from conditionally rendering the input component only when its poup opens, so I think I can use that along with :auto-focus, to get the job done.


I'll try it tonight 🙂


heya! what is the right way to go about making a :graphql-fx that uses :http-fx. I originally made a :graphql-fx that did the http calls directly but it feels a bit wrong


or should I write a graphql->http interceptor?


@andre hrmm I tried replicating the problem by deliberating changing an assoc-in to assoc and nothing bad happened. It's odd because I have had this problem where re-frisk would no longer display its contents and just print an error in the debugging popup. So it must be something else that is the trigger. It's happened a couple of times, if it happens again I will try and be more mindful about what's going on.


I’m looking for a way to do “debounced dispatch” or “delayed subscription update” to avoid GUI responsiveness issues due to expensive subscription calculations. Does anyone have an idea?


hello everyone, sorry for the basic question but .. looking at the re-frame example i see


(defn main-panel []
  (let [active-panel (re-frame/subscribe [:active-panel])]
    (fn []
     [show-panel @active-panel])))


show-panel is a function, why there is no parentheses around it?


@plins See this wiki article: TLDR: “the square version will be more efficient at “re-render time”. Only the DOM which needs to be re-rendered will be done”


thank you, i ll dig deeper in the wiki 🙂


You’re welcome. Notice the pages in the right hand menu in the wiki. At least for me they are collapsed by default and only shows “Pages 28”, instead of listing them.