Skip to content

Commit 8d1ab12

Browse files
techlabtechlab
committed
first commit
0 parents  commit 8d1ab12

Some content is hidden

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

47 files changed

+3123
-0
lines changed

‎.github/FUNDING.yml

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# These are supported funding model platforms
2+
3+
github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
4+
patreon: # Replace with a single Patreon username
5+
open_collective: # Replace with a single Open Collective username
6+
ko_fi: # Replace with a single Ko-fi username
7+
tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
8+
community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
9+
liberapay: # Replace with a single Liberapay username
10+
issuehunt: # Replace with a single IssueHunt username
11+
otechie: # Replace with a single Otechie username
12+
custom: ['https://www.paypal.me/dipuraj']

‎.github/ISSUE_TEMPLATE/bug_report.md

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. Scroll down to '....'
18+
4. See error
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected to happen.
22+
23+
**Screenshots**
24+
If applicable, add screenshots to help explain your problem.
25+
26+
**Desktop (please complete the following information):**
27+
- OS: [e.g. iOS]
28+
- Browser [e.g. chrome, safari]
29+
- Version [e.g. 22]
30+
31+
**Smartphone (please complete the following information):**
32+
- Device: [e.g. iPhone6]
33+
- OS: [e.g. iOS8.1]
34+
- Browser [e.g. stock browser, safari]
35+
- Version [e.g. 22]
36+
37+
**Additional context**
38+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/feature_request.md

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

‎.github/pull_request_template.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
### Fixes:
2+
-
3+
-
4+
-
5+
6+
### Changes:
7+
-
8+
-
9+
-
10+
11+
12+
### Thank you for your contribution!
13+
14+
Please note the following points for pull request
15+
16+
- Make sure that the pull request is not a duplicate.
17+
- Follow the same code style as the library.
18+
- Pull request should target the `dev` branch.
19+
- Don't alter the licence headers.
20+
- Run the test suites in the `test` directory first by running `npm test` or `gulp test`.
21+
- Don't modify any files in the `dist` directory.
22+
- Link any issue that is related to the pull request.
23+
- Provide a description of your changes.
24+
25+
IMPORTANT: Please review the [CONTRIBUTING.md](../CONTRIBUTING.md) file for detailed contributing guidelines.
26+
27+
**YOU CAN REMOVE THIS PR TEMPLATE BEFORE SUBMITTING**

‎.gitignore

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# See https://help.github.com/ignore-files/ for more about ignoring files.
2+
3+
# dependencies
4+
/node_modules/
5+
/bower_components/
6+
/vendor/
7+
/public/
8+
9+
# builds
10+
build
11+
dist
12+
13+
# misc
14+
.DS_Store
15+
.env
16+
.env.local
17+
.env.development.local
18+
.env.test.local
19+
.env.production.local
20+
21+
npm-debug.log*
22+
yarn-debug.log*
23+
yarn-error.log*
24+
25+
# IDE Files
26+
#-------------------------
27+
/nbproject/
28+
.idea/*
29+
.vscode/*
30+
31+
## Sublime Text cache files
32+
*.tmlanguage.cache
33+
*.tmPreferences.cache
34+
*.stTheme.cache
35+
*.sublime-workspace
36+
*.sublime-project
37+
/nbproject/private/
38+
/ref.txt

‎.npmignore

+64
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
.*.swp
2+
._*
3+
.DS_Store
4+
.git
5+
.github
6+
.hg
7+
.lock-wscript
8+
.svn
9+
.wafpickle-*
10+
CVS
11+
npm-debug.log
12+
13+
*.seed
14+
*.log
15+
*.csv
16+
*.dat
17+
*.out
18+
*.pid
19+
*.gz
20+
*.orig
21+
*.jql.js
22+
23+
work
24+
build
25+
src
26+
test
27+
spec
28+
pids
29+
logs
30+
results
31+
coverage
32+
lib-cov
33+
html-report
34+
xunit.xml
35+
36+
# IDE Files
37+
#-------------------------
38+
/nbproject/*
39+
.idea/*
40+
.vscode/*
41+
.project
42+
.idea
43+
.settings
44+
.iml
45+
46+
## Sublime Text cache files
47+
*.tmlanguage.cache
48+
*.tmPreferences.cache
49+
*.stTheme.cache
50+
*.sublime-workspace
51+
*.sublime-project
52+
53+
ehthumbs.db
54+
Icon?
55+
Thumbs.db
56+
.AppleDouble
57+
.LSOverride
58+
.Spotlight-V100
59+
.Trashes
60+
61+
/ref.txt
62+
/node_modules/
63+
/bower_components/
64+
/vendor/

‎.travis.yml

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
language: node_js
2+
cache: yarn
3+
node_js:
4+
- 12
5+
- 10

‎CODE_OF_CONDUCT.md

+76
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at [email protected]. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

‎CONTRIBUTING.md

+39
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# Contributing
2+
3+
## How can I contribute?
4+
- Fix a bug you found or already reported on the repository.
5+
- Add new features to the project.
6+
- Create new templates
7+
- Add new test cases.
8+
- Add documentation.
9+
- [Donate](https://www.paypal.me/dipuraj) money for the project on [![Paypal](https://img.shields.io/badge/PayPal-dipuraj-blue.svg)](https://www.paypal.me/dipuraj)
10+
11+
## How to contribute code?
12+
Here are the basic steps to get started contributing code:
13+
14+
1. Fork the repository.
15+
2. Install the dependencies, run `npm install`.
16+
3. Start the project, run `npm start`.
17+
4. Replicate the issue you're trying to fix or spec out the feature you're trying to add.
18+
5. Modify the code to fix the bug or to add the feature.
19+
6. Verify that your fix or feature works.
20+
7. Run the test cases by running `npm test`, you can also add more test cases based on your new change.
21+
8. Commit your changes with an informative description.
22+
9. Open a pull request to the repository with your new commit and a descriptive message about what the PR does.
23+
24+
Thank you for your contribution!
25+
26+
##### Notes for pull request
27+
- Follow the same code style as the library.
28+
- Run the test suites in the `test` directory first by running `npm test`.
29+
- Don't alter the licence headers.
30+
31+
## Reporting bugs
32+
#### Make sure it is a bug related to this project
33+
Before reporting the bug, please make sure that the bug is in the project and not from your own code or any other library used.
34+
35+
#### Try the latest version
36+
Bugs in the older versions of the project may have already been fixed.
37+
In order to avoid reporting known issues, make sure you are always testing against the latest release.
38+
Also make sure the problem hasn't already been reported on the repository.
39+
If not, create a new issue there and include your test case.

‎LICENSE

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
MIT License
2+
3+
Copyright (c) 2020 Dipu Raj
4+
http://techlaboratory.net
5+
6+
Permission is hereby granted, free of charge, to any person obtaining a copy
7+
of this software and associated documentation files (the "Software"), to deal
8+
in the Software without restriction, including without limitation the rights
9+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
10+
copies of the Software, and to permit persons to whom the Software is
11+
furnished to do so, subject to the following conditions:
12+
13+
The above copyright notice and this permission notice shall be included in all
14+
copies or substantial portions of the Software.
15+
16+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
17+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
19+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
20+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
21+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
22+
SOFTWARE.

0 commit comments

Comments
 (0)