You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If my understanding is right, the fact that there is this call to removeChildren in the update_children function would cancel the benefits of the diffing patch proposed by @vasilisp (see ocsigen/reactiveData#12).
The text was updated successfully, but these errors were encountered:
update_children is called just once, as an initialization step. The node is subsequently managed reactively. IIRC we need the removeChildren call there, e.g., to remove pre-existing server-side-produced children before the client-side reactive updates start.
With the diffing patch, we will be trigerring the Patch case in merge_msg, where removeChildren does not happen.
I have certainly tested Tyxml_js.R with the diffing patch, and I think it works as expected :).
At https://github.com/ocsigen/js_of_ocaml/blob/master/lib/tyxml/tyxml_js.ml#L232, there is a call to the
removeChildren
function. I was wondering if this call is indeed necessary? Because there is already aremoveChildren
call at https://github.com/ocsigen/js_of_ocaml/blob/master/lib/tyxml/tyxml_js.ml#L225 for theSet
action.If my understanding is right, the fact that there is this call to
removeChildren
in theupdate_children
function would cancel the benefits of the diffing patch proposed by @vasilisp (see ocsigen/reactiveData#12).The text was updated successfully, but these errors were encountered: