[feat] QDate: Disabled dates in years and months view #6639
Labels
Comments
|
I was able to recreate this issue. Working on adding the feature. |
mabele98
pushed a commit
to mabele98/quasar
that referenced
this issue
Apr 13, 2020
To disable months and years that do not contain available dates that are found in users options prop. BREAKING CHANGE: Referencing QDate.js file Added two computed functions called "years () " and "months ()" Functions return a list of boolean values to represent years/months A year/month is true if it should be disabled, false otherwise. Changed __getMonthsView to map through computed months Changed __getYearsView to map through computed years If either month or year is disabled, a label is used rather than button.
mabele98
pushed a commit
to mabele98/quasar
that referenced
this issue
Apr 13, 2020
To disable months and years that do not contain available dates that are found in users options prop. BREAKING CHANGE: Referencing QDate.js file Added two computed functions called "years () " and "months ()" Functions return a list of boolean values to represent years/months A year/month is true if it should be disabled, false otherwise. Changed __getMonthsView to map through computed months Changed __getYearsView to map through computed years If either month or year is disabled, a label is used rather than button.
15 tasks
Closed
15 tasks
|
Hi, do we have update on this? If the devs are still working on this, do we have a workaround on this? thanks |
|
Hello, still no release for this modification? EDIT: I'm just finding the options to fix the problem:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://codepen.io/stefanvh/pen/mdJjdNJ
When disabling dates with the
optionsattribute, only the days in the days view are affected. Functionality wise this is all that is required, but it would be nice if the years and months with only disabled days would also be disabled (without having too much of an impact on the performance of QDate).The text was updated successfully, but these errors were encountered: