feat: support component's ngOnChanges lifecycle hook #110
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timdeschryver
approved these changes
Jun 20, 2020
There was a problem hiding this comment.
This was easier than expected, thanks a lot!
If you want, feel free to add an example I think it could help other devs.
|
@all-contributors please add @miluoshi for code, tests |
|
I've put up a pull request to add @miluoshi! 🎉 |
|
🎉 This PR is included in version 9.4.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for ngOnChanges lifecycle hook.
renderandrerenderfunctions will automatically callngOnChangeswith correct arguments on component instance if defined.In case of initial render the
ngOnChangesis called beforengOnInit- the same behavior as in real Angular runtime.related issues: #56