-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
[RNKC-051] - fabric support #64
Conversation
…sending NaN as progress in onKeyboardMove)
} from 'react-native/Libraries/Types/CodegenTypes'; | ||
import codegenNativeComponent from 'react-native/Libraries/Utilities/codegenNativeComponent'; | ||
|
||
type KeyboardMoveEvent = Readonly<{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think similar data structure is already defined as NativeEvent
in native.ts
. Would it be possible to use one source of truth?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving type declaration into separate file will cause an error during pods installation 🤷♂️
Description
Added basic support for new (fabric) architecture.
Motivation and Context
The reason of prioritising a fabric adoption is an ability to perform sync communication between Native and JS thread. Especially it may become handy during the implementation of interactive keyboard on Android.
Current implementation allows to use both (old - paper, and new - fabric) architectures.
Unfortunately, it seems like Swift is not supported in new arch, so I had to rewrite some files to ObjC. I hope at some point of time we will bring it back to Swift.
Changelog
CI
cpplint
as C++ codebase most likely will be increased over development iterations;JS
isFabricEnabled
andisTurboModuleEnabled
variables;iOS
.m
to.mm
to support C++;Android
How Has This Been Tested?
Tested manually on:
Checklist