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
{{ message }}
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
In recent versions (can't say from exactly when), there seems to be an off-by-one error in dcc.DatePickerRange. I set max_date_allowed = datetime.today().date(), but in the calendar, yesterday is the maximum date allowed. I see it in my apps, and it is also present in the first example on the DatePickerRange documentation page.
I've also tried connecting callbacks to State("date_range", "max_date_allowed"), and there the received max date is today's date, so it only appears in the frontend.
Tested with server under both Windows 10 1909 and Linux Mint 19.1, and in both Google Chrome 85.0 and Firefox 80.0. Versions:
1. Fix requires converting max_date_allowed and min_date_allowed into
moment.js date objects.
2. Added test to cover the scenario reported in [plotly#867](plotly#867)
In recent versions (can't say from exactly when), there seems to be an off-by-one error in dcc.DatePickerRange. I set
max_date_allowed = datetime.today().date()
, but in the calendar, yesterday is the maximum date allowed. I see it in my apps, and it is also present in the first example on the DatePickerRange documentation page.Example:
I've also tried connecting callbacks to
State("date_range", "max_date_allowed")
, and there the received max date is today's date, so it only appears in the frontend.Tested with server under both Windows 10 1909 and Linux Mint 19.1, and in both Google Chrome 85.0 and Firefox 80.0. Versions:
Reported this previously in the Dash repo, but realised this is where it belongs.
The text was updated successfully, but these errors were encountered: