-
-
Notifications
You must be signed in to change notification settings - Fork 452
Description
Describe the feature
Currently, there does not seem to be a way to get direct access to the currently selected dates from RangeCalendar.
This is because the v-model seems to represent the last valid dateRange instead of the current selection.
This means it does not reflect when a user deselects the range or only selects a start date — instead, it shows an outdated selection.
I'm opening this issue because I'm not quite sure what the best solution would be.
The easiest workaround would be to add update:endValue.
This would make it possible to track the changes manually, but it would require quite a bit of code for the user.
Another option would be to add a v-model:rawDateRange which represents the selected dateRange, including undefined values.
Alternatively, the current v-model could adopt the behavior of v-model:rawDateRange, but that would be a breaking change — so probably not the best option.
Additional information
- I intend to submit a PR for this feature.
- I have already implemented and/or tested this feature.