Make RNMBXCameraComponentView prop conversions type-safe by adding Dynamic suffix and explicit unwrapping #3850
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.
Description
Summary
This PR makes the followUserLocation React-prop-to-native assignment in
RNMBXCameraComponentView.mm
fully type-safe and self-documenting by:boolValue
for boolean propsProblem
id
(e.g. assigning anNSNumber*
directly to aBOOL
, or anNSString*
to anNSString*
) can lead to silent failures, unpredictable defaults, or crashes if the JS payload doesn’t exactly match the expected type.Fixes #3794
Checklist
CONTRIBUTING.md
yarn generate
in the root folder/example
app./example
)