fix: `minimumDate` and `maximumDate` with (milli)seconds prevents onChange to be called (#760)

.maestro/minimum-date.yml

@@ -29,6 +29,14 @@ tags:
 - runFlow: utils/swipe-wheel-3-up.yml
 - assertVisible: '2000-01-01 23:59:00'
 
+### test: should ignore seconds and milliseconds
+- runFlow:
+    file: utils/change-minimum-date.yml
+    env:
+      VALUE: '2000-01-01 23:59:59.999'
+- runFlow: utils/swipe-wheel-2-up.yml
+- assertVisible: '2000-01-01 23:59:00'
+
 ### test: date mode
 
 - runFlow: utils/change-mode-date.yml

src/DatePickerAndroid.js

@@ -27,7 +27,14 @@ class DatePickerAndroid extends React.PureComponent {
 
     if (props.modal) return null
 
-    return <NativeComponent {...props} onChange={this._onChange} />
+    return (
+      <NativeComponent
+        {...props}
+        maximumDate={this._withoutSecond(props.maximumDate)}
+        minimumDate={this._withoutSecond(props.minimumDate)}
+        onChange={this._onChange}
+      />
+    )
   }
 
   getId = () => {
@@ -110,6 +117,13 @@ class DatePickerAndroid extends React.PureComponent {
     this.isClosing = true
     this.props.onCancel()
   }
+
+  _withoutSecond = (date) => {
+    if (!date) return date
+    date.setSeconds(0)
+    date.setMilliseconds(0)
+    return date
+  }
 }
 
 export default DatePickerAndroid