我对其他人一无所知，但我更喜欢使用react-redux的connect decorator包装我的组件，以便仅将我需要的商店中的道具传递到我的组件中。从某种意义上说，这证明了使用上下文是合理的，因为我没有使用它（而且我通常知道，我负责的任何代码都不会使用它）。

测试组件时，我将测试未包装的组件。因为react-redux仅通过了我在该组件上需要的道具，所以我现在确切地知道在编写测试时需要哪些道具。

我想要指出的是，我从没在代码中看到单词上下文，没有使用它，因此在某种程度上，它不会影响我！这并没有说明Facebook的“实验性”警告。如果上下文消失，在Redux更新之前，我将像其他所有人一样陷入困境。

Context is an advanced feature and is subject to change. In some cases its conveniences outweigh its downsides so some libraries like React Redux and React Router choose to rely on it despite the experimental nature.

The important part here is the word libraries. If context changes its behavior, we as library authors will need to adjust. However, as long as the library doesn’t ask you to directly use the context API, you as the user shouldn’t have to worry about changes to it.

React Redux uses context internally but it doesn’t expose this fact in the public API. So you should feel much safer using context via React Redux than directly because if it changes, the burden of updating the code will be on React Redux and not you.

Ultimately React Redux still supports always passing store as a prop so if you want to completely avoid context, you have that choice. However I would say this is impractical.

TLDR: Avoid using context directly unless you really know what you are doing. Using a library that happens to rely on context internally is relatively safe.