[TM] Add spec for Networking #24892
[TM] Add spec for Networking #24892
Conversation
facebook-github-bot
added
CLA Signed
react-native-bot
added
the
Type: Enhancement
thymikee
force-pushed
the
feat/type-networking-module
branch
from
c8e635b
to
fd48334
Compare
| callback: (requestId: number) => mixed, | ||
| ) => void; | ||
| +abortRequest: (requestId: number) => void; | ||
| +clearCookies: (callback: (result: boolean) => mixed) => void; |
There was a problem hiding this comment.
not sure if mix is understood by the codegen, but i would err towards no.
There was a problem hiding this comment.
@rickhanlonii we need your powers here
There was a problem hiding this comment.
Why does a callback have a return value?
I don't see any other usages of mixed like this
There was a problem hiding this comment.
changing to void right now
There was a problem hiding this comment.
Oh, this change. Please see this comment: #24892 (comment) what do you think?
There was a problem hiding this comment.
@RSNara could you please advise here? Is using mixed for callbacks supported by codegen? Or if we want users to be able to pass async callbacks we should return Promise<void> | void instead of just void?
| import * as TurboModuleRegistry from 'TurboModuleRegistry'; | ||
| import type {NativeResponseType} from './XMLHttpRequest'; | ||
|
|
||
| type Header = [string, string]; |
There was a problem hiding this comment.
not sure if Tuples are supported, should be interesting!
This is what we concluded with @rickhanlonii since there are 2 methods with different signatures, and Flow wasn't happy with |
|
Probably the best we can do until we unify the native interface to use the same prop types |
There was a problem hiding this comment.
@fkgozali has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
|
This pull request was successfully merged by @thymikee in e8037cb. When will my fix make it into a release? | Upcoming Releases |
Summary: Part of facebook#24875, adds a spec for Networking. Since `sendRequest` methods are different for both platforms, I had to create 2 spec files as Flow would merge their definitions even when I added `Platform.OS` check ## Changelog [General] [Added] - TM spec for Networking Pull Request resolved: facebook#24892 Reviewed By: RSNara Differential Revision: D15543067 Pulled By: fkgozali fbshipit-source-id: 2b91114dfa45e7899bbb139656a30a6fd52e31db
Summary
Part of #24875, adds a spec for Networking. Since
sendRequestmethods are different for both platforms, I had to create 2 spec files as Flow would merge their definitions even when I addedPlatform.OScheckChangelog
[General] [Added] - TM spec for Networking
Test Plan
Flow passes.