Skip to content

Commit ca191ec

Browse files
tgpetrovtgpetrov
committed
Initial commit
0 parents  commit ca191ec

File tree

296 files changed

+5667
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

296 files changed

+5667
-0
lines changed

‎.github/issue_template.md

+28
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
### Make sure to check the demo app(s) for sample usage
2+
3+
### Make sure to check the existing issues in this repository
4+
5+
### If the demo apps cannot help and there is no issue for your problem, tell us about it
6+
Please, ensure your title is less than 63 characters long and starts with a capital
7+
letter.
8+
9+
### Which platform(s) does your issue occur on?
10+
- iOS/Android/Both
11+
- iOS/Android versions
12+
- emulator or device. What type of device?
13+
14+
### Please, provide the following version numbers that your issue occurs with:
15+
16+
- CLI: (run `tns --version` to fetch it)
17+
- Cross-platform modules: (check the 'version' attribute in the
18+
`node_modules/tns-core-modules/package.json` file in your project)
19+
- Runtime(s): (look for the `"tns-android"` and `"tns-ios"` properties in the `package.json` file of your project)
20+
- Plugin(s): (look for the version numbers in the `package.json` file of your
21+
project and paste your dependencies and devDependencies here)
22+
23+
### Please, tell us how to recreate the issue in as much detail as possible.
24+
Describe the steps to reproduce it.
25+
26+
### Is there any code involved?
27+
- provide a code example to recreate the problem
28+
- (EVEN BETTER) provide a .zip with application or refer to a repository with application where the problem is reproducible.

‎.github/pull_request_template.md

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
<!--
2+
We, the rest of the NativeScript community, thank you for your
3+
contribution!
4+
To help the rest of the community review your change, please follow the instructions in the template.
5+
-->
6+
7+
<!-- PULL REQUEST TEMPLATE -->
8+
<!-- (Update "[ ]" to "[x]" to check a box) -->
9+
10+
## PR Checklist
11+
12+
- [ ] The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
13+
- [ ] There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
14+
- [ ] All existing tests are passing
15+
- [ ] Tests for the changes are included
16+
17+
## What is the current behavior?
18+
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
19+
20+
## What is the new behavior?
21+
<!-- Describe the changes. -->
22+
23+
Fixes/Implements/Closes #[Issue Number].
24+
25+
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
26+
27+
<!--
28+
BREAKING CHANGES:
29+
30+
31+
[Describe the impact of the changes here.]
32+
33+
Migration steps:
34+
[Provide a migration path for existing applications.]
35+
-->
36+

‎.gitignore

+25
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
.vscode/
2+
.idea/
3+
node_modules/
4+
*.js
5+
*.js.map
6+
*.esm.json
7+
*.tns.json
8+
*.metadata.json
9+
*.log
10+
!demo/karma.conf.js
11+
!demo/app/tests/*.js
12+
demo/platforms/
13+
demo-angular/platforms/
14+
demo-vue/platforms/
15+
!demo/e2e-tests/*
16+
!demo-vue/app/app.js
17+
*.aar
18+
/src/*.tgz
19+
*.d.ts
20+
!*index.d.ts
21+
!*datetimepicker.d.ts
22+
!*date-picker-field.d.ts
23+
!*time-picker-field.d.ts
24+
/publish/package/*.tgz
25+
/publish/package/**/*

‎CODE_OF_CONDUCT.md

+83
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
# NativeScript Community Code of Conduct
2+
3+
Our community members come from all walks of life and are all at different stages of their personal and professional journeys. To support everyone, we've prepared a short code of conduct. Our mission is best served in an environment that is friendly, safe, and accepting; free from intimidation or harassment.
4+
5+
Towards this end, certain behaviors and practices will not be tolerated.
6+
7+
## tl;dr
8+
9+
- Be respectful.
10+
- We're here to help.
11+
- Abusive behavior is never tolerated.
12+
- Violations of this code may result in swift and permanent expulsion from the NativeScript community channels.
13+
14+
## Administrators
15+
16+
- Dan Wilson (@DanWilson on Slack)
17+
- Jen Looper (@jen.looper on Slack)
18+
- TJ VanToll (@tjvantoll on Slack)
19+
20+
## Scope
21+
22+
We expect all members of the NativeScript community, including administrators, users, facilitators, and vendors to abide by this Code of Conduct at all times in our community venues, online and in person, and in one-on-one communications pertaining to NativeScript affairs.
23+
24+
This policy covers the usage of the NativeScript Slack community, as well as the NativeScript support forums, NativeScript GitHub repositories, the NativeScript website, and any NativeScript-related events. This Code of Conduct is in addition to, and does not in any way nullify or invalidate, any other terms or conditions related to use of NativeScript.
25+
26+
The definitions of various subjective terms such as "discriminatory", "hateful", or "confusing" will be decided at the sole discretion of the NativeScript administrators.
27+
28+
## Friendly, Harassment-Free Space
29+
30+
We are committed to providing a friendly, safe, and welcoming environment for all, regardless of gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics.
31+
32+
We ask that you please respect that people have differences of opinion regarding technical choices, and acknowledge that every design or implementation choice carries a trade-off and numerous costs. There is seldom a single right answer. A difference of technology preferences is never a license to be rude.
33+
34+
Any spamming, trolling, flaming, baiting, or other attention-stealing behaviour is not welcome, and will not be tolerated.
35+
36+
Harassing other users of NativeScript is never tolerated, whether via public or private media.
37+
38+
Avoid using offensive or harassing package names, nicknames, or other identifiers that might detract from a friendly, safe, and welcoming environment for all.
39+
40+
Harassment includes, but is not limited to: harmful or prejudicial verbal or written comments related to gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics; inappropriate use of nudity, sexual images, and/or sexually explicit language in public spaces; threats of physical or non-physical harm; deliberate intimidation, stalking or following; harassing photography or recording; sustained disruption of talks or other events; inappropriate physical contact; and unwelcome sexual attention.
41+
42+
## Acceptable Content
43+
44+
The NativeScript administrators reserve the right to make judgement calls about what is and isn't appropriate in published content. These are guidelines to help you be successful in our community.
45+
46+
Content must contain something applicable to the previously stated goals of the NativeScript community. "Spamming", that is, publishing any form of content that is not applicable, is not allowed.
47+
48+
Content must not contain illegal or infringing content. You should only publish content to NativeScript properties if you have the right to do so. This includes complying with all software license agreements or other intellectual property restrictions. For example, redistributing an MIT-licensed module with the copyright notice removed, would not be allowed. You will be responsible for any violation of laws or others’ intellectual property rights.
49+
50+
Content must not be malware. For example, content (code, video, pictures, words, etc.) which is designed to maliciously exploit or damage computer systems, is not allowed.
51+
52+
Content name, description, and other visible metadata must not include abusive, inappropriate, or harassing content.
53+
54+
## Reporting Violations of this Code of Conduct
55+
56+
If you believe someone is harassing you or has otherwise violated this Code of Conduct, please contact the administrators and send us an abuse report. If this is the initial report of a problem, please include as much detail as possible. It is easiest for us to address issues when we have more context.
57+
58+
## Consequences
59+
60+
All content published to the NativeScript community channels is hosted at the sole discretion of the NativeScript administrators.
61+
62+
Unacceptable behavior from any community member, including sponsors, employees, customers, or others with decision-making authority, will not be tolerated.
63+
64+
Anyone asked to stop unacceptable behavior is expected to comply immediately.
65+
66+
If a community member engages in unacceptable behavior, the NativeScript administrators may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event or service).
67+
68+
## Addressing Grievances
69+
70+
If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the administrators. We will do our best to ensure that your grievance is handled appropriately.
71+
72+
In general, we will choose the course of action that we judge as being most in the interest of fostering a safe and friendly community.
73+
74+
## Contact Info
75+
Please contact Dan Wilson @DanWilson if you need to report a problem or address a grievance related to an abuse report.
76+
77+
You are also encouraged to contact us if you are curious about something that might be "on the line" between appropriate and inappropriate content. We are happy to provide guidance to help you be a successful part of our community.
78+
79+
## Credit and License
80+
81+
This Code of Conduct borrows heavily from the WADE Code of Conduct, which is derived from the NodeBots Code of Conduct, which in turn borrows from the npm Code of Conduct, which was derived from the Stumptown Syndicate Citizen's Code of Conduct, and the Rust Project Code of Conduct.
82+
83+
This document may be reused under a Creative Commons Attribution-ShareAlike License.

‎CONTRIBUTING.md

+75
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
# Contributing to NativeScript DateTimePicker
2+
3+
:+1: First of all, thank you for taking the time to contribute! :+1:
4+
5+
Here are some guides on how to do that:
6+
7+
<!-- TOC depthFrom:2 -->
8+
9+
- [Code of Conduct](#code-of-conduct)
10+
- [Reporting Bugs](#reporting-bugs)
11+
- [Requesting Features](#requesting-features)
12+
- [Submitting a PR](#submitting-a-pr)
13+
- [Where to Start](#where-to-start)
14+
15+
<!-- /TOC -->
16+
17+
## Code of Conduct
18+
Help us keep a healthy and open community. We expect all participants in this project to adhere to the [NativeScript Code Of Conduct](https://github.com/NativeScript/codeofconduct).
19+
20+
21+
## Reporting Bugs
22+
23+
1. Always update to the most recent master release; the bug may already be resolved.
24+
2. Search for similar issues in the issues list for this repo; it may already be an identified problem.
25+
3. If this is a bug or problem that is clear, simple, and is unlikely to require any discussion -- it is OK to open an issue on GitHub with a reproduction of the bug including workflows and screenshots. If possible, submit a Pull Request with a failing test, entire application or module. If you'd rather take matters into your own hands, fix the bug yourself (jump down to the [Submitting a PR](#submitting-a-pr) section).
26+
27+
## Requesting Features
28+
29+
1. Use Github Issues to submit feature requests.
30+
2. First, search for a similar request and extend it if applicable. This way it would be easier for the community to track the features.
31+
3. When requesting a new feature, please provide as much detail as possible about why you need the feature in your apps. We prefer that you explain a need rather than explain a technical solution for it. That might trigger a nice conversation on finding the best and broadest technical solution to a specific need.
32+
33+
## Submitting a PR
34+
35+
Before you begin make sure there is an issue for the bug or feature you will be working on.
36+
37+
Following these steps is the best way to get your code included in the project:
38+
39+
1. Fork and clone the nativescript-datetimepicker repo:
40+
```bash
41+
git clone https://github.com/NativeScript/nativescript-datetimepicker.git
42+
# Navigate to the newly cloned directory
43+
cd nativescript-datetimepicker
44+
# Add an "upstream" remote pointing to the original repo.
45+
git remote add upstream https://github.com/NativeScript/nativescript-datetimepicker.git
46+
```
47+
48+
2. Read our [development workflow guide](DevelopmentWorkflow.md) for local setup
49+
50+
3. Create a branch for your PR
51+
```bash
52+
git checkout -b <my-fix-branch> master
53+
```
54+
55+
4. The fun part! Make your code changes. Make sure you:
56+
- Follow the [code conventions guide](https://github.com/NativeScript/NativeScript/blob/master/CodingConvention.md).
57+
- Follow the [commit message guidelines](https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#-commit-message-guidelines)
58+
- Update the README if you make changes to the plugin API
59+
60+
5. Before you submit your PR:
61+
- Rebase your changes to the latest master: `git pull --rebase upstream master`.
62+
- Ensure your changes pass tslint validation. (run `npm run tslint` in the `src` folder).
63+
64+
6. Push your fork. If you have rebased you might have to use force-push your branch:
65+
```
66+
git push origin <my-fix-branch> --force
67+
```
68+
69+
7. [Submit your pull request](https://github.com/NativeScript/nativescript-datetimepicker/compare) and compare to `NativeScript/nativescript-datetimepicker`. Please, fill in the Pull Request template - it will help us better understand the PR and increase the chances of it getting merged quickly.
70+
71+
It's our turn from there on! We will review the PR and discuss changes you might have to make before merging it! Thanks!
72+
73+
## Where to Start
74+
75+
If you want to contribute, but you are not sure where to start - look for issues labeled [`help wanted`](https://github.com/NativeScript/nativescript-datetimepicker/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22).

‎DevelopmentWorkflow.md

+48
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Development Workflow
2+
3+
<!-- TOC depthFrom:2 -->
4+
5+
- [Prerequisites](#prerequisites)
6+
- [Develop locally](#develop-locally)
7+
8+
<!-- /TOC -->
9+
10+
11+
## Prerequisites
12+
13+
* Install your native toolchain and NativeScript as [described in the docs](https://docs.nativescript.org/start/quick-setup)
14+
15+
* Review [NativeScript plugins documentation](https://docs.nativescript.org/plugins/plugins) for more details on plugins development
16+
17+
18+
## Develop locally
19+
20+
For local development we recommend using the npm commands provided in the plugin's package.json
21+
22+
Basically executing a bunch of commands will be enough for you to start making changes to the plugin and see them live synced in the demo. It's up to you to decide which demo to use for development - TypeScript, TypeScript + Angular or TypeScript + Vue.
23+
24+
25+
To run and develop using TypeScript demo:
26+
```bash
27+
$ cd nativescript-datetimepicker/src
28+
$ npm run demo.ios
29+
$ npm run demo.android
30+
```
31+
32+
To run and develop using TypeScript + Angular demo:
33+
```bash
34+
$ cd nativescript-datetimepicker/src
35+
$ npm run demo.ng.ios
36+
$ npm run demo.ng.android
37+
```
38+
39+
To run and develop using TypeScript + Vue demo:
40+
```bash
41+
$ cd nativescript-datetimepicker/src
42+
$ npm run demo.vue.ios
43+
$ npm run demo.vue.android
44+
```
45+
46+
After all the changes are done make sure to test them in all the demo apps.
47+
48+
For details on plugins development workflow, read [NativeScript plugins documentation](https://docs.nativescript.org/plugins/building-plugins#step-2-set-up-a-development-workflow) covering that topic.

0 commit comments

Comments
 (0)