- The provider component puts the data into context, and the Higher Order Component pulls the data out of context.
- The first pull request to that repository is from Andrew Clark (react core team member) and it’s called “New version of context”.
- , but if that’s not your jam, you could easily implement a Higher Order Component or something else using the context API (which is why it’s the best).
- The React team will remove the warning about context being an experimental feature because it’s now a “first-class feature” of the framework.
- One question that I’ve seen a lot about the new context API (or the render prop pattern in general) is how to compose providers and consumers together.
React’s new context API way more ergonomic, it’s no longer “experimental,” and it’s now a first-class API! OH, AND IT USES A RENDER PROP!
It’s way more ergonomic, it’s no longer “experimental,” and it’s now a first-class API! OH, AND IT USES A RENDER PROP!
NOTE: This is a cross-post from my newsletter . I publish each email to my blog two weeks after it’s sent. Subscribe to get more content like this earlier right in your inbox! 💌
Have you heard of the context API in React? If you’ve heard of it, are you like many others afraid to use it directly because you saw this in the official docs:
The first result of that search is showing “Why Not To Use Context”. Doesn’t inspire a whole lot of confidence in the context API. To make things even more concerning, that section says:
Have you ever experienced the pain of trying to get state from the top of your react tree to the bottom? This pain you’re feeling is called “prop drilling” and it’s super annoying. You wind up having to pass props through components that don’t care about the data just so you can send it down to components that do care. And as you move components around this pain is magnified.