Cheng Lou
11 years ago
committed by
Connor McSheffrey
2 changed files with 25 additions and 0 deletions
@ -0,0 +1,10 @@ |
|||
--- |
|||
id: componentWillReceiveProps-not-triggered-after-mounting-tip |
|||
title: componentWillReceiveProps not triggered after mounting |
|||
layout: docs |
|||
permalink: componentWillReceiveProps-not-triggered-after-mounting-tip.html |
|||
--- |
|||
|
|||
`componentWillReceiveProps` isn't triggered after the node is put on scene. This is by design. Checkout [other lifecycle methods](component-specs.html) for the one that suits your needs. |
|||
|
|||
The reason for that is because `componentWillReceiveProps` often handles the logic of comparing with the old props and act upon changes; not triggering it at mounting, where there are no old props, clearly defines what the method should do. |
@ -0,0 +1,15 @@ |
|||
--- |
|||
id: componentWillReceiveProps-not-triggered-after-mounting |
|||
title: componentWillReceiveProps not triggered after mounting |
|||
layout: docs |
|||
permalink: componentWillReceiveProps-not-triggered-after-mounting.html |
|||
--- |
|||
|
|||
### Problem |
|||
`componentWillReceiveProps` isn't triggered after the node is put on scene. |
|||
|
|||
### Solution |
|||
This is by design. Checkout [other lifecycle methods](component-specs.html) for the one that suits your needs. |
|||
|
|||
### Discussion |
|||
`componentWillReceiveProps` often handles the logic of comparing with the old props and act upon changes; not triggering it at mounting, where there are no old props, clearly defines what the method should do. |
Loading…
Reference in new issue