not sure sorry, gtg

@danielcompton: No problem. Will figure it out. Thanks again for all the help.

Is there a sane way to update a local-state atom when a handler has been..finished?

say I have some (render-foo [] (let [loaded (r/atom false]] (fn [] [render something based on atom value)

and I want to update loaded in some way after some async data in a background has returned

(that this function really doesnt have knowledge of)

other than a reaction to it rerunning this

The particular use case is I have a form that I want to pre-fill when that data is finally loaded

@bpicolo: when the other one come back, it needs to call a new handler

Mike Thompson's undo/redo made me think how awesome it'd be for re-frame to have something like CoreObject's UI https://www.youtube.com/watch?v=KD8xa3ku1qA (hat tip to @conaw)

https://egghead.io/lessons/javascript-getting-started-with-redux-dev-tools

Its interesting, Redux can do some pretty interesting stuff because all mutations to state are just immutable events that are reduced over to achieve final state. Makes it real easy to remove something from history and have it change state. I wonder how one might get same sort of experience with Re-frame

@darwin I don't follow your last point. The profile String is in Clojure on the server from the initial GET request to start the app. Without putting it in the JS space in the returned bootstrap html page with (javascript-tag ...), how would the re-com GUI access the String?

@symbit: go into DevTools js console and type document.location

the html page has access to current url, you can parse it with javascript

if I understand it correctly from your last snippet, you obtain title and profile values from request url, which is exactly the same url seen on client-side

@darwin I see it. gotcha. Thank you!

@conaw: easy to do the same in re-frame (since before redux existed :-)) if someone wants to create the chrome extension.