Skip to content

Commit 7d0fc0d

Browse files
felixheckfelixheck
committed
initial
0 parents  commit 7d0fc0d

23 files changed

+7516
-0
lines changed

‎.editorconfig‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# editorconfig.org
2+
root = true
3+
4+
[*]
5+
indent_style = space
6+
indent_size = 2
7+
end_of_line = lf
8+
charset = utf-8
9+
trim_trailing_whitespace = true
10+
insert_final_newline = true
11+
12+
[*.md]
13+
trim_trailing_whitespace = false

‎.gitignore‎

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
### custom ###
2+
.idea
3+
.vscode
4+
5+
### Node ###
6+
# Logs
7+
logs
8+
*.log
9+
npm-debug.log*
10+
11+
# Runtime data
12+
pids
13+
*.pid
14+
*.seed
15+
*.pid.lock
16+
17+
# Directory for instrumented libs generated by jscoverage/JSCover
18+
lib-cov
19+
20+
# Coverage directory used by tools like istanbul
21+
coverage
22+
23+
# nyc test coverage
24+
.nyc_output
25+
26+
# Compiled binary addons (http://nodejs.org/api/addons.html)
27+
build/Release
28+
29+
# Dependency directories
30+
node_modules
31+
jspm_packages
32+
33+
# Optional npm cache directory
34+
.npm
35+
36+
# Optional REPL history
37+
.node_repl_history
38+
39+
40+
### Linux ###
41+
*~
42+
43+
# temporary files which can be created if a process still has a handle open of a deleted file
44+
.fuse_hidden*
45+
46+
# KDE directory preferences
47+
.directory
48+
49+
# Linux trash folder which might appear on any partition or disk
50+
.Trash-*
51+
52+
53+
### macOS ###
54+
*.DS_Store
55+
.AppleDouble
56+
.LSOverride
57+
58+
# Icon must end with two \r
59+
Icon
60+
61+
62+
# Thumbnails
63+
._*
64+
65+
# Files that might appear in the root of a volume
66+
.DocumentRevisions-V100
67+
.fseventsd
68+
.Spotlight-V100
69+
.TemporaryItems
70+
.Trashes
71+
.VolumeIcon.icns
72+
.com.apple.timemachine.donotpresent
73+
74+
# Directories potentially created on remote AFP share
75+
.AppleDB
76+
.AppleDesktop
77+
Network Trash Folder
78+
Temporary Items
79+
.apdisk

‎.nvmrc‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
6

‎.travis.yml‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
language: node_js
2+
3+
node_js:
4+
- 6
5+
- node
6+
7+
before_script:
8+
- npm install
9+
10+
script:
11+
- npm run lint
12+
- npm test
13+
14+
after_script:
15+
- npm run ci.coverage

‎CODE_OF_CONDUCT.md‎

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
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, gender identity and expression, level of experience,
9+
nationality, personal appearance, race, religion, or sexual identity and
10+
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 [http://contributor-covenant.org/version/1/4][version]
72+
73+
[homepage]: http://contributor-covenant.org
74+
[version]: http://contributor-covenant.org/version/1/4/

‎CONTRIBUTING.md‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
# Contributing to laabr
2+
3+
First and foremost, thank you! I appreciate that you want to contribute to laabr, your time is valuable, and your contributions mean a lot to me.
4+
5+
## Important!
6+
7+
By contributing to this project, you:
8+
9+
* Agree that you have authored 100% of the content
10+
* Agree that you have the necessary rights to the content
11+
* Agree that you have received the necessary permissions from your employer to make the contributions (if applicable)
12+
* Agree that the content you contribute may be provided under the Project license
13+
14+
## Getting started
15+
16+
**What does "contributing" mean?**
17+
18+
Creating an issue is the simplest form of contributing to a project. But there are many ways to contribute, including the following:
19+
20+
- Updating or correcting documentation
21+
- Feature requests
22+
- Bug reports
23+
24+
**Showing support for laabr**
25+
26+
Please keep in mind that open source software is built by people like you, who spend their free time creating things the rest the community can use.
27+
28+
Don't have time to contribute? No worries, here are some other ways to show your support for laabr:
29+
30+
- star the [project](https://github.com/felixheck/laabr)
31+
- tweet your support for laabr
32+
33+
## Issues
34+
35+
### Before creating an issue
36+
37+
Please try to determine if the issue is caused by an underlying library, and if so, create the issue there. Sometimes this is difficult to know. I only ask that you attempt to give a reasonable attempt to find out. Oftentimes the readme will have advice about where to go to create issues.
38+
39+
Try to follow these guidelines
40+
41+
- **Avoid creating issues for implementation help**. It's much better for discoverability, SEO, and semantics - to keep the issue tracker focused on bugs and feature requests - to ask implementation-related questions on [stackoverflow.com][so] or send a mail/tweet.
42+
- **Investigate the issue**
43+
- **Check the readme** - oftentimes you will find notes about creating issues, and where to go depending on the type of issue.
44+
- Create the issue in the appropriate repository.
45+
46+
### Creating an issue
47+
48+
Please be as descriptive as possible when creating an issue. Give me the information I need to successfully answer your question or address your issue by answering the following in your issue:
49+
50+
- **version**: please note the version of laabr are you using
51+
- **extensions, plugins, helpers, etc** : please list any extensions you're using
52+
- **error messages**: please paste any error messages into the issue, or a [gist](https://gist.github.com/)
53+
54+
### Closing issues
55+
56+
The original poster or the maintainer's of laabr may close an issue at any time. Typically, but not exclusively, issues are closed when:
57+
58+
- The issue is resolved
59+
- The project's maintainers have determined the issue is out of scope
60+
- An issue is clearly a duplicate of another issue, in which case the duplicate issue will be linked.
61+
- A discussion has clearly run its course
62+
63+
[so]: http://stackoverflow.com/questions/tagged/laabr

‎LICENSE‎

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

0 commit comments

Comments
 (0)