Investigate MorphDOM vs ReactDOM

未關閉
#883 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
javascript, python, react
領域
frontend

研究方向

Start by reviewing the reactpy.html.script behavior and the original discussion in https://github.com/idom-team/idom/discussions/798. Compare how ReactDOM currently handles client-side DOM changes with the proposed MorphDOM alternative. Done means documenting a clear decision on whether to adopt MorphDOM or address the ReactDOM mismatch another way.

由索引模型根據 Issue 內容生成。

描述

priority-3-low type-investigation

Currently, due to the addition of our reactpy.html.script tag, there is now the potential of user's manually manipulating the client side DOM, which will cause a mismatch when comparing to the server side VDOM. This can cause client side exceptions within ReactDOM when the attempting to change/modify/add/delete nodes or attributes that no longer exist. We may want to consider switching to MorphDOM to account for this, since it could automatically mutate the client DOM to meet the server side VDOM model.

This issue exists to debate whether MorphDOM should be considered as an alternative, or whether we should simply work around these issues with React-DOM.

Note: Originally discussed in https://github.com/idom-team/idom/discussions/798 by Archmonger August 10, 2022

主要語言
Python
星號
8.1k
分支
332
30 天內沒有已合併 PR

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

reactive-python/reactpy 的其他 Issue

查看 reactive-python/reactpy 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。