makeomatic/redux-connect

filter-ed promises not being executed in componentDidMount

Open

#30 建立於 2016年6月16日

在 GitHub 查看
 (6 留言) (0 反應) (0 負責人)JavaScript (550 star) (73 fork)batch import
bugenhancementhelp wanted

描述

BEGIN_GLOBAL_LOAD/END_GLOBAL_LOAD are dispatched on the client side even when filter stops the asyncConnect from blocking the render function. However, once the component is mounted, since the redux has saved the state loaded as true, it does not fetch the data. Due to this you have to manually redo the logic for re-fetching data in these instances. It would be nice to have some logic to ascertain that the promise is executed in componentDidMount.

貢獻者指南

技術棧
javascriptreact
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
familiarity with redux connectReact component lifecycleJavaScript promises
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Examine the `asyncConnect` decorator implementation in the redux connect source code, focusing on how the `filter` prop affects promise execution and state management in `componentDidMount`. Review the issue comments for additional context and potential solutions. Consider creating a minimal reproduction and testing the expected behavior.