React provides a number of powerful patterns to compose components; for example, Containment, Specialization, and Render Props. Today we’ll dive into the Containment pattern which, on the surface, looks like an easy-to-understand interface — but the example provided in React docs doesn't have an explicit explanation of how to pass data from the parent container to its children.
Hey all! So, we continue working on our app. We already know how to make simple calls to the server and for 80% of possible cases this knowledge will be enough for executing standard tasks. However, we will learn how to deal with more complicated things, too. So, before moving on toward this task, I’d like to warn you that middleware does not necessarily need to be written by yourself. It means these are such frequently used (re-used) elements that have already been written previously by someone else. We recommend you to explore this resource, where you will find a whole bunch of various middlewares and so on. For example, here is a ready-to-use logger. We’ve created a logger to practice a little bit, but here is an example of a perfect ready-to-use solution.
Our topic for today deals with asynchronous actions. We will start to take our articles from API. As you have already noticed, we have a simple API working. And in order to launch it, you need to open the folder simple_api and execute the following command there:
Hey all! Right now we will check up your home task and give you some valuable comments that will help you with your future work with React. To make it more convenient, you will need to see your code, so, switch to the respective commit and we will continue. Let us start with connect. We need connect to work with store. There is also another way: if you can transmit data using common props – do it! For example, in containers/Articles.js we refer to store in order to take out the needed articles from state: