Fix iOS Codegen fallback for libraries without an iOS config - #57790
Fix iOS Codegen fallback for libraries without an iOS config#57790RealBhupesh wants to merge 1 commit into
Conversation
|
Hi @RealBhupesh! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Hi React Native maintainers, I’ve completed the Meta CLA for this contribution. This PR is ready for review when convenient. It includes a regression test covering component libraries without an iOS Codegen config. Thank you! |
|
signed it |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Summary
iosblock.Changelog:
[IOS] [FIXED] - iOS Codegen now discovers third-party component libraries without an iOS configuration.
Fixes #55308
Test plan
yarn jest packages/react-native/scripts/codegen/__tests__/generate-artifacts-executor-test.js --runInBand --testNamePattern="crawls component libraries without an iOS config"fs.rmdirSync(..., {recursive: true}).