React Router moved away from a route config approach to routing to a component based approach. However, if you need it, you can still have a central route config with React Router. In this post, we'll walk through how by breaking down the 'Route Config' example on the React Router docs.
The React documentation, as well as other examples that show the use of Context, describe cases where common data such as locale or theme is stored on a higher level of the tree and is consumed, using the API, by components further down. In this post, Boris will try to describe a different approach to using Context, and the benefits of it when thinking of component composition.
Render props still a bit confusing? This article does a really great job of breaking them down in an easily consumable way.
This article talks about using a pattern over a library for state management. Using a pattern instead of a library means that you have more freedom. You are not dependent on a library’s features, bug fixes, and release dates. You are not worried about backward compatibility, deprecation, upgrade migration paths, or project abandonment. You are never waiting for a missing feature.