🐛 Refactor DatePicker component to handle null startDate date range selection properly #5782
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Linked issue: #5759
Problem
As mentioned in the linked ticket, we are having an issue when the user tries to clear the
startDatevalue (when theendDateis available) using the date input, suddenly the datepicker becomes unresponsive. User can't see any value in the date input and they won't be able to select any new value from the date picker popup also.Changes
startDate&endDateis null. Because the current logic is returning empty string when thestartDateis not available regardless of checking the existence of theendDateendDateis available. It'll either set thestartDateby retaining the endDate (if its less than the existingendDate) or set thestartDateby clearing theendDate(If the existingendDateis less than the currentstartDate).endDateis availableContribution checklist