feat(VDateInput): parse text field value in locale aware way #19955
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.
fixes #19803
fixes #19951
Description
Changes to the v-date-input:
multiple = range
, then blur/enter now correctly handles parsing, which resolves [Bug Report][3.6.8] v-date-input multiple="range" doesn't respond to text input #19951multiple = true
, then blur/enter do nothing; and thev-text-field
is automatically set into a readonly mode{x} selected
, so it makes no sense to parse that value at all into a date; this way nothing can be typed into the text field, but the end user can still select dates in the pickerThe
dateFromLocalizedValue
function was implemented that can be reused in other places if needed. It was not implemented in the adapter, as it will break thedate-io
interface, so it is just an internal implementation.Currently, that function is only supporting parsing the string value from the
keyboardDate
format, but if needed, it can be extended for other use cases (e.g., for future VTimeInput to support similar use case as in VDateInput)Markup: