Lifecycle methods and Context API from React 16.3
See original GitHub issueThe official React 16.3 release is still upcoming, but there are several highly anticipated features whose implementation could start now: https://medium.com/@baphemot/whats-new-in-react-16-3-d2c9b7b6193b
Particularly the new Context API, which could be built on top of the existing API for now.
Also important to implement will be static getDerivedStateFromProps
, which replaces ~componentDidMount
~ componentWillReceiveProps
(and is allegedly necessary for async rendering).
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:7 (3 by maintainers)
Top Results From Across the Web
React v16.3.0: New lifecycles and context API
In React 16.3.0, we are adding a few new lifecycle methods to assist with that migration. We are also introducing new APIs for...
Read more >React 16.3 Lifecycle Methods
This method is called after a component is instantiated and when the component receives new props. Since it is a static method, you...
Read more >New in React 16.3: an Official Context API, Better ...
The context API lets developers streamline the access to data provided to React components. Typically, such data is passed down from one level ......
Read more >React 16.3: What's New?
React 16.3 ships with new lifecycle methods such as getDerivedStateFromProps , and getSnapshotBeforeUpdate . The current lifecycle methods ...
Read more >Explain new lifecycle methods in React v16.3
React 16.3 has introduced some major updates like the new Ref API, lifecycle hooks changes, and much more. Right now, we will be...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@kylealwyn you’re right, my mistake! Well, I thought
componentDidMount
was faster to type, and maybe no one would notice… 😄Small edit:
static getDerivedStateFromProps
will be replacingcomponentWillReceiveProps
, notcomponentDidMount