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

Possible that rn-fetch-blob will go unmaintained #53

Closed
davidpaulhunt opened this issue Dec 7, 2020 · 3 comments
Closed

Possible that rn-fetch-blob will go unmaintained #53

davidpaulhunt opened this issue Dec 7, 2020 · 3 comments

Comments

@davidpaulhunt
Copy link

According to this issue, rn-fetch-blob may go unmaintained.

Is this something we should worry about? If so, how can we help to ensure this project doesn't suffer? How can we (or I) help?

Feel free to close this if you are aware or already have a plan.

Cheers.

@robwalkerco
Copy link
Owner

There are several other similar projects that use different storage options. Perhaps redux-persist-fs-storage may be better to use long-term?
There are others listed on the redux-persist readme

It should be possible to move data from one system to another without effecting users. You will need to load data from one redux-persist config, and use that to hydrate another.

Perhaps I should add a notice to the readme regarding

@davidpaulhunt
Copy link
Author

@robwalkerco Cool, appreciate the feedback!

@robwalkerco
Copy link
Owner

I have just published version v4.0.0 which switches the dependancy from rn-fetch-blob to react-native-blob-util

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

No branches or pull requests

2 participants