Fixed for supporting flow

[ifsnow]

It is the same as the PR that I submitted in react-native repository.

I hope this helps.

[cpojer]

Wow, nice. Thank you! I'll leave it to @krizzu to review and merge this PR. :)

[krizzu]

Thanks for the first contribution 💪
I've left one suggestion to consider, let me know what you think.

[krizzu]

What about exporting this to different file, say types/flow.js and then include it in .flowconfig?

[ifsnow]

@krizzu
There is some troubles when using .flowconfig. For example, hyperlink(Go to definition) in vscode does not work properly.

I think the approach below looks ok.

• Added AsyncStorageType.js to define types and separated it from AsyncStorage.js.
• Added AsyncStorageType.js.flow to provide more clean autocomplete.

Let me know what you think about this.

[krizzu]

On the second thought, having types defined in the same file is better than have 2 different files with types. Thought extracting flow types into another file would be better supported by VScode.

If you would revert 1 commit back, I'd be more than happy to merge it 👍
Sorry for confusion!

[ifsnow]

@krizzu Sure. I had a similar idea. I modified it as you said.

[krizzu]

Great, thank You.
In that case, where we have Types in the same file, do we still need .js.flow file? Any advantages to having it?
Also, can you rebase with master, please?

[ifsnow]

@krizzu With AsyncStorage.js.flow, we can use more organized auto-completion in VSCode, but I realized there was a problem with the function to jump directly to AsyncStorage.js to check the code.

It seemed to have more disadvantages than merits, so I decided to delete AsyncStorage.js.flow. Sorry for confusion!

I finished what you said.

[krizzu]

Thanks!