Improve usability of the initiate()
action for mutations.
#4337
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.
When running requests by manually dispatching the
initiate()
action the usability of mutation endpoints is worse than queries.When using a query you can easily check for the presence of a
data
orerror
prop in the union returned to make decisions. For example:In the case of mutation that code will have a type error:
Infact the only typesafe way to read the data or error property is to do something like this:
The reason it works for queries is because each entry in the discriminated union always includes an explicit
error
anddata
property, set to undefined if it's not included in that case.This PR makes the same change to the return type for mutations.