Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Use new Context API in React 16.3
See original GitHub issueThere’s a new render prop/children-as-function API for context that just came in React 16.3.0.
The big thing that’s relevant to us: It works across shouldComponentUpdate boundaries without the need for subscriptions.
It will require some refactoring. And backward compatibility is going to be…interesting. We may have to drop backward compatibility to make the implementation clean. FWIW, React Router and React Redux is considering this too, so we’re not alone.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:11
- Comments:18 (17 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I would prefer dropping support for React < 16.3 in 1.0.0. People will hate us, but they’ll need to effectively rewrite their app anyway when they update. Also, React 16.x is very stable, API-wise, so upgrading from React 16.0 to 16.3 to 16.x should be easy.
Regarding the metrics of the package: Didn’t look at that, missing issues and 1.4 kB overhead are a pretty big no-go.
@leMaik We will at least drop React < 16.0 support between 1.0.0-beta.x and 1.0.0. It’s a matter of timing. If the react team release React 17.0 in one year from now, I think that we can wait Material-UI 2.0.0 otherwise, as you say.