-
Notifications
You must be signed in to change notification settings - Fork 723
docs: be more specific about current Angular's rerender behavior #1213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: be more specific about current Angular's rerender behavior #1213
Conversation
✅ Deploy Preview for testing-library ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
781c472
to
af8cd40
Compare
docs/angular-testing-library/api.mdx
Outdated
@@ -411,8 +411,8 @@ expect(screen.getByTestId('name-value').textContent).toBe('Sarah') | |||
|
|||
### `rerender` | |||
|
|||
Re-render the same component with different props. Input properties that are not | |||
defined are cleared. This calls `detectChanges` after the props are updated. | |||
Create and render a new instance of the component. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to keep a note about "Input properties that are not
defined are cleared.".
Now that I see this, this is also the reason that change
and rerender
exist.
With change you can't clear input properties.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the PR. Please let me know what you think. I also created testing-library/angular-testing-library#365 for further discussion. Thanks again for your great fast responses :)
@all-contributors please add @shaman-apprentice for docs |
I've put up a pull request to add @shaman-apprentice! 🎉 |
ref #653