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.
filter-ed promises not being executed in componentDidMount · makeomatic/redux-connect#30 | Good First Issue