-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
[ReactNative][Docs] Document how to link libraries #300
[ReactNative][Docs] Document how to link libraries #300
Conversation
|
||
### Step 3 | ||
|
||
The first two steps will be enough for all libraries that we ship we Ract Native |
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.
s/we Ract Native/with React Native
On the same sort of topic - I was going to have a stab at I found this a bit difficult/time consuming when writing RCTVibration with my limited XCode experience and it could encourage consistency and best practices around exports, docs etc. It would make each plugin nicely |
Oh, I'll fix this typo, thanks! The |
The article looks good, but maybe still pretty complex for non-ios developer who sees Xcode for the first time. Would be nice to add a screenshot. Ideally we would do all the work using something like As for |
5964ed0
to
b06cdf0
Compare
[ReactNative][Docs] Document how to link libraries
* Update scripts to publish react-native-macos-init * Clean up merge markers * Start of run-macos cli * run-macos working * Add JSDoc * Fix script to only pass argument when installed * Fixed var name * Added run-macs CI step * Log success or failure
…t-empty-component chore add ListEmptyComponent to FlatList
Add some documentation on how to link the libraries that we built as independent xcode projects.
/cc @vjeux @a2