Legacy storage

[krizzu]

This task involves reusing existing AsyncStorage implementation with the new API. New API available here.

To do:

• Initial implementation of Legacy storage (thanks to @jeremyscatigna)

• Setup an example to use said storage

• Storage creation options (while instantiating):

  • Support for different app groups paths on iOS (reference here)
  • Support for different location for async storage (reference here)

• Add flags as storage options:

  • Flag to tell if multi* operation should fail whole operation or just one and continue with the rest (reference here)

References:

• multiGet does not report errors #105
• Serial Executor hangs on Android 9 #84

This issue will be updated with any upcoming ideas/suggestions.

Blocked

#131

[BrodaNoel]

@krizzu question: If there are not going to be breaking changes, so, why are you considering changing the version number to 2.x.x?

[krizzu]

@BrodaNoel There are breaking changes regarding API you use (RFC available here, but no breaking changes in terms of stored data.

So you'll have to update your codebase to use new API (if you decide to move on to v2), but your users won't lose data stored.

[poltak]

Are the "Storage creation options" tasks still planned for v2?
I just saw this issue was closed and those tasks not checked off, so I wasn't entirely sure of the intention. Cheers :)