a291642c53
in VisionCamera v1 & v2 there were two ObjC macros that were helping in creation/registration of Frame Processors, but these were removed with v3 This PR reintroduces such macros, which will not only make FP development easier, but also it will also fix issues people had with registration of Swift Frame Processors (+load vs +initialize issues) Docs were also updated to reflect that the macros should be used to correctly initialize and register ObjC/Swift Frame Processors |
||
---|---|---|
.. | ||
Core | ||
Extensions | ||
Frame Processor | ||
Parsers | ||
React Utils | ||
Types | ||
VisionCamera.xcodeproj | ||
.swift-version | ||
.swiftformat | ||
.swiftlint.yml | ||
CameraBridge.h | ||
CameraDevicesManager.m | ||
CameraDevicesManager.swift | ||
CameraView.swift | ||
CameraView+Focus.swift | ||
CameraView+RecordVideo.swift | ||
CameraView+TakePhoto.swift | ||
CameraView+Zoom.swift | ||
CameraViewManager.m | ||
CameraViewManager.swift | ||
README.md |
ios
This folder contains the iOS-platform-specific code for react-native-vision-camera.
Prerequesites
- Install Xcode tools
xcode-select --install
- Install need SwiftFormat and SwiftLint
brew install swiftformat swiftlint
Getting Started
It is recommended that you work on the code using the Example project (example/ios/VisionCameraExample.xcworkspace
), since that always includes the React Native header files, plus you can easily test changes that way.
You can however still edit the library project here by opening VisionCamera.xcodeproj
, this has the advantage of automatically formatting your Code (swiftformat) and showing you Linter errors (swiftlint) when trying to build (⌘+B).
Committing
Before committing, make sure that you're not violating the Swift or C++ codestyles. To do that, run the following command:
yarn check-ios
This will also try to automatically fix any errors by re-formatting the Swift code.