fix(ios): fix nullability warnings (#36247)

Summary:
While testing `use_frameworks! :linkage => :static`, I encountered nullability warnings that were previously suppressed because we always build with `-Werror`. I'm not sure why the suppressions no longer work, but they should just be fixed.

## Changelog

[IOS] [FIXED] - Fix nullability warnings

Pull Request resolved: https://github.com/facebook/react-native/pull/36247

Test Plan: iOS build should succeed.

Reviewed By: cipolleschi

Differential Revision: D43531887

Pulled By: javache

fbshipit-source-id: cae0617a20c8d215042cf4c5be2cbb17c801bb41
This commit is contained in:
Tommy Nguyen
2023-02-24 03:54:02 -08:00
committed by Facebook GitHub Bot
parent a7f962c469
commit 346b028227
2 changed files with 13 additions and 5 deletions
+5 -1
View File
@@ -7,12 +7,16 @@
@class RCTSource;
NS_ASSUME_NONNULL_BEGIN
/**
* This protocol should be adopted when a turbo module needs to tell React Native to load a script.
* In bridge-less React Native, it is a replacement for [_bridge loadAndExecuteSplitBundleURL:].
*/
@protocol RCTJSScriptLoaderModule <NSObject>
@property (nonatomic, copy, nonnull) void (^loadScript)(RCTSource *source);
@property (nonatomic, copy) void (^loadScript)(RCTSource *source);
@end
NS_ASSUME_NONNULL_END