generated from calcit-lang/calcit-workflow
-
Notifications
You must be signed in to change notification settings - Fork 0
hot swapping
jiyinyiyong edited this page Sep 1, 2021
·
1 revision
Hot swapping is done by the compiler. What you need to do is to call respo.core/clear-cache!
before re-rendering happens:
defn reload! ()
; "clear component caches"
clear-cache!
; "rerender DOM tree, I mean, a diff/patch loop"
render-app!
println "|Code update."
If you don't, in the next rendering phase old element tree would be used if no argument changes found, which means Respo would still use render functions defined previously.
In Respo, you are asked to define *store
explicitly. They the global states of data. As an Atom, the value inside is immutable, but the reference is mutable. During hot swapping, variables defined with defatom
will be retained. As a result, component states are persistent even code is swapped:
defatom *store $ atom
or
let
raw $ or
js/localStorage.getItem "|respo"
, "|{:data [], :states {}}"
read-string raw
, schema/store