Skip to content

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Feb 9, 2023
Merged

docs: be more specific about current Angular's rerender behavior #1213

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
af8cd40
docs: be more specific about current Angular's rerender behavior
shaman-apprentice Feb 5, 2023
581248f
docs: restore hint that not defined input properties are cleared
shaman-apprentice Feb 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/angular-testing-library/api.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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. Input properties that are not
defined are cleared. To keep them use [change](#change).

```typescript
const {rerender} = await render(Counter, {
Expand Down