-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
feat(b-calendar, b-form-datepicker): add optional decade navigation buttons (addresses #4976) #5112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #5112 +/- ##
=======================================
Coverage 99.95% 99.95%
=======================================
Files 277 277
Lines 6522 6522
Branches 1612 1612
=======================================
Hits 6519 6519
Misses 3 3 Continue to review full report at Codecov.
|
|
@jackmu95 Do you think the decade buttons should be opt-in (as current in this PR, set prop to show), or opt-out (shown by default, set prop to hide)? Current opt-in demo: https://deploy-preview-5112--bootstrap-vue.netlify.com/docs/components/calendar#internationalization We could make the decade buttons automatic by default (depending on the range for |
Describe the PR
Adds new prop
show-decade-navto enable optional +/- decade navigationAddresses parts of #4976
To Do:
b-calendarunit testsb-form-datepickerb-calendardocsb-form-datepickerdocsPR checklist
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
The PR fulfills these requirements:
devbranch, not themasterbranch[...] (fixes #xxx[,#xxx]), where "xxx" is the issue number)fix(alert): not alerting during SSR render,docs(badge): update pill examples,chore(docs): fix typo in README, etc). This is very important, as theCHANGELOGis generated from these messages.If new features/enhancement/fixes are added or changed:
package.jsonfor slot and event changes)If adding a new feature, or changing the functionality of an existing feature, the PR's
description above includes: