fix(types) Correct overload order for act without strictNullChecks in TypeScript #622
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:
Correct the TypeScript definitions, so that we produce the correct return type for
act(...)
calls whenstrictNullChecks
is turned off.Why:
Take the following code
With
strictNullChecks
turned on, the type ofresult
isPromise<undefined>
as you would expect.Turn
strictNullChecks
off, and the type ofresult
is nowvoid
.This is particularly highlighted in my case as the project I'm working on has eslint rules that will complain if we try to await a value it thinks is not thenable.
How:
It seems the issue is that with
strictNullChecks
, the two overloads foract(...)
do not have a lot of overlap so the order we specify them in doesn't matter. WithoutstrictNullChecks
, anything that matches the async overload also matches the sync overload. Since the sync overload is specified first, it is always chosen.I've just swapped the overloads around so that the more specific one with Promises is checked first.
Checklist: