React Is it bad if presentation components contain container components?

Question

According to https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0#.i63w9pvzw

Presentation components:

• It can contain both presentation and container components inside, and usually has some DOM markup and its own styles.
• Regardless of other applications, such as activities or Flux stores.

I think that if presentation components contain container components, they will get dependent on Flux or Redux (or what container components depend on).

This makes it difficult to test and reuse presentation components.

Answer 1

Not bad, that's great. The whole point of react-redux is that you can directly connect the container components to the repository, without passing the entire store to each component as a support, Component reuse is not a problem, since the <Provider> component will create any connected container components where- something lower.

It is actually not difficult to check the container components. You can make the connected component a standard export, but also export the unconnected component as a named export, which you can use for tests, and manually pass it to the requisites in these tests. See the Related Components section of the 'Writing Tests' section of the Redux docs for more information.

As for testing presentation components containing container components, this will not be a problem. Shallow rendering will still work in tests (if you are not using this problem ). And if you need to mount a component in a test, you can always wrap it in a <Provider> component with a repository specific to this test.

Edit: This answer is specific to Redux with a-redux reaction. Other Flux implementations may have some difficulties with this that I am not aware of.