When using dash version 4.2.0, dcc.DatePicker does not wait until the end date is picked, despite updatemode=‘bothdates’. Is this a known bug? This keeps me to moving from dash 3.4.0 to 4.2.0.
Thank you @eklaassen for letting us know. I informed the engineering team. It’s also reported on GitHub .
Thanks Adam, I added some additional info there.
There is now a PR to fix this
dev ← bugfix/3425-datepicker-bothdates
opened 04:03PM - 10 Jun 26 UTC
Fixes a bug in `DatePickerRange` when `updatemode="bothdates"`.
To reproduce:…
1. Create a `DatePickerRange` attached to a callback:
```python
dcc.DatePickerRange(
start_date=date(2021, 1, 1),
end_date=date(2021, 1, 31),
updatemode="bothdates",
id="dpr",
),
```
2. Start a new date selection by changing the dates
3. Observe that the callback fires before both dates are selected (`updatemode` not respected)
Fixes #3425
## Contributor Checklist
- [x] I have run the tests locally and they passed. (refer to testing section in [contributing](https://github.com/plotly/dash/blob/master/CONTRIBUTING.md))
- [x] I have added tests, or extended existing tests, to cover any new features or bugs fixed in this PR
### optionals
- [x] I have added entry in the `CHANGELOG.md`
