-
-
Notifications
You must be signed in to change notification settings - Fork 616
fix(openapi-react-query): mutation results type #2519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
👷 Deploy request for openapi-ts pending review.Visit the deploys page to approve it
|
🦋 Changeset detectedLatest commit: bec703f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
89090ce to
ffc9e6d
Compare
|
Tests fail due to a refactor in Redocly's test folder structure (unrelated to this PR's change), I've opened a separate PR to address that here #2522 |
282876f to
ded751e
Compare
|
@htunnicliff could you please merge this PR? 🙏🏼 |
|
Thanks for adding! Could you please add a changeset (see comment)? |
ded751e to
bec703f
Compare
Thanks for checking this PR! I've updated the branch & added the changset 👍 |
Changes
Adds proper types to the useMutation's onMutateResults fields which are used in
onSettled,onError& return object of this hook.The open issue regarding this bug: #2518
I ended up digging further & this seems to fix it, but looking forward for a second pair of eyes to check that my fix is correct 🙂
Here I moved the
Optionstype definition from the generic parameters to the actualoptionsparameter themselves, thus not setting theUseMutationOptions'sTOnMutateResultto the defaultunknown.How to Review
Checklist
docs/updated (if necessary)pnpm run update:examplesrun (only applicable for openapi-typescript)