feat: add rerender method #257
Merged
Conversation
This file contains 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
BREAKING CHANGE:
rerender has been renamed to change
change keeps the current fixture intact and invokes ngOnChanges
the new rerender method destroys the current component and creates a new instance
with the updated properties
BEFORE:
const { rerender } = render(...)
rerender({...})
AFTER:
const { change } = render(...)
change({...})
Closed
|
🎉 This PR is included in version 11.0.0-beta.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
timdeschryver
added a commit
that referenced
this pull request
Dec 3, 2021
BREAKING CHANGE:
`rerender` has been renamed to `change`.
The `change` method keeps the current fixture intact and invokes `ngOnChanges`.
The new `rerender` method destroys the current component and creates a new instance with the updated properties.
BEFORE:
```ts
const { rerender } = render(...)
rerender({...})
```
AFTER:
```ts
const { change } = render(...)
change({...})
```
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.
Closes #252
BREAKING CHANGE:
rerender has been renamed to change
change keeps the current fixture intact and invokes ngOnChanges
the new rerender method destroys the current component and creates a new instance
with the updated properties
BEFORE:
const { rerender } = render(...)
rerender({...})
AFTER:
const { change } = render(...)
change({...})