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

fix(persist): introduce in-house synchronous Storage interface #3672

Closed
wants to merge 4 commits into from

Conversation

todorone
Copy link
Contributor

@todorone todorone commented Jun 6, 2022

Rationale

Currently RQ has createWebStoragePersistor and createAsyncStoragePersistor which assumes that non-web platforms can have async storages only, which is not true. React Native has performant synchronous MMKV adapters support, which can't be used with RQ 3 right now directly because of interface incompatibility and window check(already fixed in v4).
Related discussion: #3667

Changes

Introduce own Storage interface to make possible using createWebStoragePersistor in React Native without TS errors.

@vercel
Copy link

vercel bot commented Jun 6, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
react-query ✅ Ready (Inspect) Visit Preview Jun 6, 2022 at 5:48AM (UTC)

@codesandbox-ci
Copy link

codesandbox-ci bot commented Jun 6, 2022

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit e9d38d6:

Sandbox Source
tannerlinsley/react-query: basic Configuration
tannerlinsley/react-query: basic-typescript Configuration

@TkDodo
Copy link
Collaborator

TkDodo commented Jun 6, 2022

thanks. can you make a PR towards the beta branch ?

@todorone todorone changed the base branch from master to beta June 6, 2022 05:45
@todorone
Copy link
Contributor Author

todorone commented Jun 6, 2022

thanks. can you make a PR towards the beta branch ?

Oops, missed this point, sorry.
Is it ok now?

I mean do You do squash commits 'cause it's a dirty history now

@TkDodo
Copy link
Collaborator

TkDodo commented Jun 6, 2022

there are conflicts now because we've renamed the directory - in v4, the plugin is no longer experimental

@todorone todorone closed this Jun 6, 2022
@todorone
Copy link
Contributor Author

todorone commented Jun 6, 2022

there are conflicts now because we've renamed the directory - in v4, the plugin is no longer experimental

sorry for a mess, created new "clean" PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants