You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting the value through MaterialDateTimePicker#data(newValue) doesn't set the value correctly, and overloading data for get/set is not a friendly API design.
Bug: picker.set(newDatetime) does not set the picker's time where newDatetime differs from the picker's current time in both date and time.
Add get, which always returns the current value as a moment
Add a deprecation warning to data() / data(nextValue). Mark for removal in a future release.
Fix behaviour of set where both the date and time change
The text was updated successfully, but these errors were encountered:
Setting the value through
MaterialDateTimePicker#data(newValue)
doesn't set the value correctly, and overloadingdata
for get/set is not a friendly API design.Bug:
picker.set(newDatetime)
does not set the picker's time wherenewDatetime
differs from the picker's current time in both date and time.get
, which always returns the current value as amoment
data()
/data(nextValue)
. Mark for removal in a future release.set
where both the date and time changeThe text was updated successfully, but these errors were encountered: