Skip to content
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

[3.8 beta] Support returnPartialData and refetchWritePolicy in useBackgroundQuery #10893

Closed
alessbell opened this issue May 18, 2023 · 2 comments · Fixed by #10960
Closed

[3.8 beta] Support returnPartialData and refetchWritePolicy in useBackgroundQuery #10893

alessbell opened this issue May 18, 2023 · 2 comments · Fixed by #10960
Assignees
Milestone

Comments

@alessbell
Copy link
Contributor

Issue Description

In the initial implementation, returnPartialData and refetchWritePolicy were omitted from the accepted options type. Since these are supported options in useSuspenseQuery, we should support them in useBackgroundQuery.

One concern to be aware of is that the QueryReference type returned by the hook accounts for whether data is partial data or not.

Link to Reproduction

N/A

Reproduction Steps

No response

@alessbell alessbell self-assigned this May 18, 2023
@jerelmiller jerelmiller added this to the Release 3.8 milestone May 26, 2023
@alessbell alessbell linked a pull request Jun 9, 2023 that will close this issue
3 tasks
@jerelmiller jerelmiller changed the title [3.8 alpha] Support returnPartialData and refetchWritePolicy in useBackgroundQuery [3.8 beta] Support returnPartialData and refetchWritePolicy in useBackgroundQuery Jun 15, 2023
@alessbell
Copy link
Contributor Author

Closed via #10960.

@github-actions
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using StackOverflow or our discord server.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants