feat: add a new methods isYearDisabled, isMonthDisabled for disabling unavailable months, year #140
Conversation
This file contains 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
|
Thanks, this is a great enhancement, could you make this PR compatible with v3 and resolve the conflicts? |
mystica2000
force-pushed
the
feat/disable-month-year-selection
branch
from
31c4d0a to
282d132
Compare
|
compatible with v3 and resolved conflicts via rebase |
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.
Intent
Allow disabling of the year and month selection when they are restricted/unavailable via minDate and maxDate.
Proposed changes
Created two new Utils for isMonthDisabled and isYearDisabled check similar to date's isDateDisabled
Demo (in the example app comments - minDate,maxDate):
Does this introduce a breaking change?
closes:
#118
#108