Feature: InputDate and InputDateRange Enhancements#672
Merged
maartenbreddels merged 4 commits intowidgetti:masterfrom Jul 3, 2024
Merged
Feature: InputDate and InputDateRange Enhancements#672maartenbreddels merged 4 commits intowidgetti:masterfrom
maartenbreddels merged 4 commits intowidgetti:masterfrom
Conversation
iisakkirotko
requested changes
Jun 10, 2024
Collaborator
iisakkirotko
left a comment
There was a problem hiding this comment.
Thanks a lot for the PR and detailed explanation @brian-c-ogorman! I only had one comment. I think it would also be good to squash the last two commits into one. Otherwise looks great!
added 4 commits
June 10, 2024 11:59
Adds a "date_picker_type" parameter to let the user specify whether the date picker should use daily (the default) or monthly granularity.
Adds "min_date" and "max_date" parameters to allow the user to set limits on allowed dates.
Adds an optional "sort" parameter to allow the user to automatically sort the dates chosen with the InputDateRange. If `sort=True`, dates will be sorted in ascending order. Otherwise, the order of the dates will reflect the order that they were picked.
559c2d6 to
efcc6f0
Compare
iisakkirotko
approved these changes
Jun 11, 2024
Collaborator
iisakkirotko
left a comment
There was a problem hiding this comment.
Looks good to me. Thanks a lot for the PR!
Contributor
|
Awesome work @brian-c-ogorman ! We plan to release this soon, today maybe even. |
Collaborator
|
And it's out :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
This change adds a few enhancements to the
InputDateandInputDateRangecomponents:InputDateRangecomponent only).See here for the full discussion.
Usage
Daily granularity, with limits the min/max allowed date
Using the
min_dateandmax_dateparameters to limit selection to dates in the next two weeks:Monthly granularity, with limits on the min/max allowed date
Use
date_picker_type="month"to have an input with monthly granularity:Daily granularity, with limits the min/max allowed dates, where the output is sorted
Use
sort=Trueto automatically sort the output in ascending order:Monthly granularity, with limits the min/max allowed dates, where the output is sorted
Use
date_picker_type="month"to have an input with monthly granularity andsort=Trueto automatically sort the output in ascending order:Vuetify 3 Upgrade Path
From what I can tell, in Vuetify 3, the
minandmaxparameters are still supported by theVDatePickerobject (see here).I don't see a clear example of a date picker with monthly granularity on the component documentation here. Based on the API, it looks like they have split the "Monthly Date Picker" into a separate component, called
VDatePickerMonth(see here). There is also aVDatePickerMonthsin the API (see here), though it appears to have fewer parameters -- I am not sure how that component differs from orVDatePickerMonth.As a result, when upgrading to Vuetify 3, these components would probably be split into something like
InputDate/InputMonthandInputDateRange/InputMonthRange, based on theVDatePickerandVDatePickerMonthcomponents, respectively.