問題描述
在項目中使用 Context API 我以前會在異步操作創建者中使用 Redux？ (Using Context API in a project I would have previously used Redux in ‑ async action creators?)
所以我的大多數項目都很簡單，以至於 Redux 完全是矯枉過正（儘管它一直都很好用）——我將在一個新項目上使用 Context API（它很容易完成這項工作，而且更容易向其他開發人員解釋並讓他們繼續工作）‑ Redux 有 Thunk 來處理異步操作。我認為我對事情的理解已經足夠好，以至於異步操作不會成為 Context API 的問題——Redux Thunk 實際上並沒有向 Redux 添加異步功能——它只是讓語法更容易接受。所以我的推理是，只要我編寫代碼來正確處理它們，Context API 就能夠處理任何異步操作。這是對的嗎，或者如果我想有效地處理異步操作，我是否需要堅持使用帶有 Thunk 的 Redux？
參考解法
方法 1:
I had similar question myself and came across this article that talks about a major difference between Redux and the Context API:
From https://www.academind.com/learn/react/redux‑vs‑context‑api/
The Context API (currently) is not built for high‑frequency updates (quote of Sebastian Markbage, React Team), it’s not optimized for that. The react‑redux people ran into this problem when they tried to switch to React Context internally in their package.
My personal summary is that new context is ready to be used for low frequency unlikely updates (like locale/theme). It’s also good to use it in the same way as old context was used. I.e. for static values and then propagate updates through subscriptions. It’s not ready to be used as a replacement for all Flux‑like state propagation. ‑‑‑ Sebastian Markbage
So for the moment, it seems like you might want to look into using React Context for low‑frequency updates (e.g. theme changes, user authentication) but not use it for the general state management of your application.
Hope this helps.
(by BruceM、yoges nsamy)