Optional usage without context

I have been wondering why dependence on context is not optional.

Context is always referred to as an unstable and experimental feature, although react and redux are stable libraries widely used in production.

It seems to me that passing a configured store explicitly to connect is no harder than passing action creators to it. This would also mean that we don’t need a <Provider /> component, therefore less api surface area.

Would this update be desired? Or am I missing something and there are hidden complications i’m not considering?

[timdorr]

Oh duh, that’s right. We’ve already got this! 😄

[markerikson]

@everdimension : yeah, there’s an FAQ entry that addresses that: http://redux.js.org/docs/faq/StoreSetup.html#store-setup-multiple-stores . Basically, accessing the store via context acts as a lightweight dependency injection mechanism, thus making it easier to test components, less hassle passing the store down, component reuse, etc.