TypeScript: Improve type definition to use optional chaining #244
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.
Optional Chaining is the syntax in upcoming ECMAScript and introduced in TypeScript v3.7.
In #240, I(Sorry, account is different but it's me) changed react-refetch's type definition so that unsafe access can be detected by TS compiler.
However, sometimes people want to simplify this by using optional chaining
This PR improve type definition so that all
PromiseState
type have value field to use optional chaining for genericPromiseState
type.