vue-functional-calendar 2.9.91 → 2.9.94

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/.github/README.md CHANGED
@@ -3,13 +3,11 @@
3
3
  <h1 align="center">Vue Functional Calendar</h1>
4
4
  <p align="center">Modern calendar and datepicker module for Vue.js</p>
5
5
 
6
- [![Buy us a tree](https://img.shields.io/badge/Treeware-%F0%9F%8C%B3-lightgreen?style=for-the-badge)](https://offset.earth/treeware?gift-trees)
7
- [![Tweet](https://img.shields.io/twitter/url/http/shields.io.svg?style=social)](https://twitter.com/intent/tweet?text=Lightweight,%20high%20performance%20calendar%20component%20based%20on%20Vue.js&url=https://github.com/ManukMinasyan/vue-functional-calendar&via=github&hashtags=vue,calendar,design,developers)
8
-
9
6
  [![Build Status](https://travis-ci.org/ManukMinasyan/vue-functional-calendar.svg?branch=master)](https://travis-ci.org/ManukMinasyan/vue-functional-calendar)
10
7
  [![Version](https://img.shields.io/npm/v/vue-functional-calendar.svg)](https://www.npmjs.com/package/vue-functional-calendar)
11
8
  [![Software License](https://img.shields.io/badge/license-MIT-brightgreen.svg?style=flat-square)](LICENSE)
12
9
  [![Downloads](https://img.shields.io/npm/dt/vue-functional-calendar.svg)](https://www.npmjs.com/package/vue-functional-calendar)
10
+ [![Plant Tree](https://img.shields.io/badge/dynamic/json?color=brightgreen&label=Plant%20Tree&query=%24.total&url=https%3A%2F%2Fpublic.offset.earth%2Fusers%2Ftreeware%2Ftrees)](https://plant.treeware.earth/ManukMinasyan/vue-functional-calendar)
13
11
  ___
14
12
  ## Demo
15
13
 
@@ -169,6 +167,8 @@ ___
169
167
  | isDark | Boolean | false | true | Dark theme |
170
168
  | isLayoutExpandable | Boolean | false | true | Enable expanding the calendar layout |
171
169
  | alwaysUseDefaultClasses | Boolean | false | true | Always add default classes to Day element, even when overriding with a slot |
170
+ | activeHours | Array | [] | [8, 9,10, 18, 19, 20] | The hours you want to be shown in the timepicker (by default all of them are shown)
171
+ | activeMinutes | Array | [] | [0, 15, 30, 45] | The minutes you want to be shown in the timepicker (by default all of them are shown)
172
172
  ___
173
173
 
174
174
  ### Slots
@@ -0,0 +1,49 @@
1
+ # Contributing to Vue-Functional-Calendar
2
+ We love your feedback! We need to make adding to this task as simple and straightforward as could be expected, regardless of whether it's:
3
+
4
+ - Detailing a bug
5
+ - Examining the present status of the code
6
+ - Presenting a fix
7
+ - Proposing new highlights
8
+ - Turning into a maintainer
9
+
10
+ ## We Develop with Github
11
+ We use github to have code, to follow issues and component demands, as well as acknowledge pull requests.
12
+
13
+ ## We Use [Github Flow](https://docs.github.com/en/get-started/quickstart/github-flow), So All Code Changes Happen Through Pull Requests
14
+ Pull requests are the most ideal way to propose changes to the codebase (we use [Github Flow](https://docs.github.com/en/get-started/quickstart/github-flow)). We effectively welcome your draw demands:
15
+
16
+ 1. Fork the repo and make your branch from 'master'.
17
+ 2. Assuming you've added code that ought to be tried, add tests.
18
+ 3. On the off chance that you've changed APIs, update the documentation.
19
+ 4. Guarantee the test suite passes.
20
+ 5. Ensure your code lints.
21
+ 6. Issue that pull request!
22
+
23
+ ## Any commitments you cause will to be under the MIT Software License
24
+ To put it plainly, when you submit code changes, your entries are perceived to be under a similar [MIT License](http://choosealicense.com/licenses/mit/) that covers the task. Go ahead and contact the maintainers assuming that is a worry.
25
+
26
+ ## Report bugs utilizing Github's [issues](https://github.com/ManukMinasyan/vue-functional-calendar/issues)
27
+ We use GitHub issues to follow public bugs. Report a bug by [opening a new issue](https://github.com/ManukMinasyan/vue-functional-calendar/issues/new); it's just simple!
28
+
29
+ ## Compose bug reports with detail, foundation, and test code
30
+
31
+ **Extraordinary Bug Reports** will generally have:
32
+
33
+ - A fast outline or potentially foundation
34
+ - Steps to repeat
35
+ - Be explicit!
36
+ - Give test code if possible.
37
+ - What you expected would occur
38
+ - What really occurs
39
+ - Notes (perhaps including why you figure this may be occurring, or stuff you attempted that didn't work)
40
+
41
+ Individuals *love* exhaustive bug reports. I'm not in any event, joking.
42
+
43
+ ## Use a Consistent Coding Style
44
+
45
+ * 2 spaces for space rather than tabs
46
+ * You can have a go at running 'npm run build up' for style unification
47
+
48
+ ## License
49
+ By contributing, you concur that your commitments will be authorized under its MIT License.
package/README.md CHANGED
@@ -49,4 +49,9 @@ It’s now common knowledge that one of the best tools to tackle the climate cri
49
49
 
50
50
  You can buy trees here [offset.earth/treeware](https://offset.earth/treeware?gift-trees)
51
51
 
52
- Read more about Treeware at [treeware.earth](http://treeware.earth)
52
+ Read more about Treeware at [treeware.earth](http://treeware.earth)
53
+
54
+ ## Sponsor
55
+ ![Scheduling API](https://user-images.githubusercontent.com/9488406/125080407-0dd25780-e0c5-11eb-9f70-ef958968674a.png)
56
+
57
+ This project is sponsored by **Spurwing**, where their API Makes Adding Scheduling Quick, Reliable and Scalable. Use Spurwing to build and integrate Scheduling, Booking & Calendar features in your project. Read more about Spurwing's [**Scheduling API**](https://www.spurwing.io/).