Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this?
Adds SwiftPM support to
@react-native-harness/ui, so iOS apps using React Native's SwiftPM integration can build the native UI module without a local package patch.Fixes #212.
How does it work?
The npm package includes a
HarnessUImanifest and itsswiftpmConfigname. The manifest uses React Native's autolinking layout to resolve React headers and the generatedHarnessUISpec, and matches React's Debug/Release C++ definitions. Explicit Foundation/UIKit imports replace the imports supplied by CocoaPods' prefix header. The existing podspec remains available.The installation docs cover SwiftPM, and a version plan includes this in the next release.
Testing
Package.swiftand the native sources.pnpm build:all,pnpm lint:all,pnpm test:all, andpnpm typecheck:allpass.The native checks build the UI package in an external fixture; they do not run a full app or UI tests.
Why is this useful?
Apps can keep using Harness UI tests after moving from CocoaPods to SwiftPM. This replaces the packaging workaround used in Nitro's SwiftPM migration.