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-calendar-picker@7.0.9 for the project I'm working on because [Insert reason here].
react-native-calendar-picker@7.0.9
Here is the diff that solved my problem:
diff --git a/node_modules/react-native-calendar-picker/CalendarPicker/index.js b/node_modules/react-native-calendar-picker/CalendarPicker/index.js index c225330..c1dfb73 100644 --- a/node_modules/react-native-calendar-picker/CalendarPicker/index.js +++ b/node_modules/react-native-calendar-picker/CalendarPicker/index.js @@ -74,9 +74,7 @@ export default class CalendarPicker extends Component { let minMaxDates = {}; - if (prevProps.minDate !== this.props.minDate || - prevProps.minDate !== this.props.minDate - ) { + if (prevProps.minDate !== this.props.minDate || prevProps.maxDate !== this.props.maxDate) { minMaxDates.minDate = this.props.minDate && moment(this.props.minDate); minMaxDates.maxDate = this.props.maxDate && moment(this.props.maxDate); + + doStateUpdate = true }
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered:
Thanks @serkanekinci for finding this bug. Please submit a PR.
Sorry, something went wrong.
Fix minDate & maxDate prop change detection (#272)
a6cca80
0bea64c
Published in 7.1.1.
To speed up fixes in the future, please submit a PR instead of a patch file.
No branches or pull requests
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch
react-native-calendar-picker@7.0.9
for the project I'm working on because [Insert reason here].Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: