docs: corrects deprecation warning for waitForDomChange #478
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.
What:
If you are migrating from
waitForDomChanges
, it suggests usingwait
instead, which is also deprecated and it suggestswaitFor
. The link in this particular warning is linked towaitFor
.but then it says
wait
is also deprecated:Why:
☝️
How:
Updated deprecation warning string with the correct suggestion
Checklist:
docs site
DefinitelyTyped N/A