We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch @react-native-community/[email protected] for the project I'm working on.
@react-native-community/[email protected]
Here is the diff that solved my problem:
diff --git a/node_modules/@react-native-community/datetimepicker/ios/RNDateTimePickerShadowView.m b/node_modules/@react-native-community/datetimepicker/ios/RNDateTimePickerShadowView.m index 4ff3362..c139440 100644 --- a/node_modules/@react-native-community/datetimepicker/ios/RNDateTimePickerShadowView.m +++ b/node_modules/@react-native-community/datetimepicker/ios/RNDateTimePickerShadowView.m @@ -41,7 +41,7 @@ - (void)setTimeZoneName:(NSString *)timeZoneName { YGNodeMarkDirty(self.yogaNode); } -static YGSize RNDateTimePickerShadowViewMeasure(YGNodeConstRef node, float width, YGMeasureMode widthMode, float height, YGMeasureMode heightMode) +static YGSize RNDateTimePickerShadowViewMeasure(YGNodeRef node, float width, YGMeasureMode widthMode, float height, YGMeasureMode heightMode) { RNDateTimePickerShadowView *shadowPickerView = (__bridge RNDateTimePickerShadowView *)YGNodeGetContext(node);
The text was updated successfully, but these errors were encountered:
@muhammadhassan149 thanks so much, you save my day!
Sorry, something went wrong.
Hello and thanks for reporting, same as #911 Thank you 🙂
No branches or pull requests
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch
@react-native-community/[email protected]
for the project I'm working on.Here is the diff that solved my problem:
The text was updated successfully, but these errors were encountered: