This repository has been archived by the owner on Mar 16, 2019. It is now read-only.
Share cookies with RN, remove cookie utils #388
Merged
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.
I hope I am creating this PR the right place, as I couldn't find the branches mentioned.
This is a PR to address issues #156, #157, #220. It makes the android version share cookies with react native (regular
fetch
shares cookies withRNFetchBlob
) as it already seems to do on iOS, so the PR harmonises the behaviour on the platforms.Now that both platforms share cookies with react native, I though a very sensible move would be to remove this library's cookie-CRUD capabilities, as all use cases now can be solved by using other libraries such as
react-native-cookies
. This frees us from spending time on problems that are better solved elsewhere and focus on the main issue the library is meant to solve. It also minimises bloat as only a fraction of users will actually need to use cookie CRUD-features.I makes even more sense considering CRUD isn't really working in this library. So I say: Let others do the cookie-manipulation and lets just share cookies with react-native. It will take away a lot of confusion and pain from users (especially when the two platforms behave differently!).
I'm not too sharp in Objective-C (or Java for that matter) so some testing will need to be done.