Only Rerender "DAO Connected" Components
還沒有人認領這個 Issue。
- 主要語言
- TypeScript
- 星號
- 21
- 分支
- 9
- PR 合併指標
- 30 天內沒有已合併 PR
描述
Only rerender components that are "DAO Connected".
This can be done through supporting a subscription model, where components that depend on additional contextual information (ex: , ).
For example, consider...
```html
{data => (
)}
```
Ideally, if Arc.Config's web3 provider changes, View1 & 2 shouldn't have to rerender, but View3 should because the data may be different. This can be partially achieved if DAO connect's the Arc.Config's subscriber list, which will cause it to be told to rerender if the config ever changes, but this only causes View1 to not be rendered. View2 would still be rendered because currently the data is stored within the Component's state (the DAO's state), which would cause View2 to still be rendered.
Going to leave this here for now, as it'll be interesting to come back to this after some metrics have been gathered, as I feel this may be premature optimization.
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
首先查看 Arc.Config、DAO 和 DAO.Data 中描述的元件訂閱行為,尤其是 DAO 狀態更新如何觸發重新渲染。在決定是否推進最佳化之前,先收集提議的指標;完成的標準是確定一個經過測量且達成共識的範圍,僅重新渲染與 DAO 連線的元件。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- react, typescript
- 領域
- frontend, performance
- Issue 類型
- 重構
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100