Skip to content

Commit 1aa66e6

Browse files
NetanelBasalNetanelBasal
committed
docs: add @NetanelBasal as a contributor
1 parent b23a949 commit 1aa66e6

12 files changed

+472
-49
lines changed

‎.all-contributorsrc

+26
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
{
2+
"projectName": "forms-manager",
3+
"projectOwner": "ngneat",
4+
"repoType": "github",
5+
"repoHost": "https://github.com",
6+
"files": [
7+
"README.md"
8+
],
9+
"imageSize": 100,
10+
"commit": true,
11+
"commitConvention": "angular",
12+
"contributors": [
13+
{
14+
"login": "NetanelBasal",
15+
"name": "Netanel Basal",
16+
"avatar_url": "https://avatars1.githubusercontent.com/u/6745730?v=4",
17+
"profile": "https://www.netbasal.com",
18+
"contributions": [
19+
"code",
20+
"doc",
21+
"ideas"
22+
]
23+
}
24+
],
25+
"contributorsPerLine": 7
26+
}

‎CODE_OF_CONDUCT.md

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

‎CONTRIBUTING.md

+75
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
# Contributing to Transloco
2+
3+
🙏 We would ❤️ for you to contribute to Transloco and help make it even better than it is today!
4+
5+
# Developing
6+
7+
Start by installing all dependencies:
8+
9+
```bash
10+
npm i
11+
```
12+
13+
Run the tests:
14+
15+
```bash
16+
npm test
17+
npm run e2e
18+
```
19+
20+
Run the playground app:
21+
22+
```bash
23+
npm start
24+
```
25+
26+
## Building
27+
28+
```bash
29+
npm run build
30+
```
31+
32+
## <a name="rules"></a> Coding Rules
33+
34+
To ensure consistency throughout the source code, keep these rules in mind as you are working:
35+
36+
- All features or bug fixes **must be tested** by one or more specs (unit-tests).
37+
- All public API methods **must be documented**.
38+
39+
## <a name="commit"></a> Commit Message Guidelines
40+
41+
We have very precise rules over how our git commit messages can be formatted. This leads to **more
42+
readable messages** that are easy to follow when looking through the **project history**. But also,
43+
we use the git commit messages to **generate the Akita changelog**.
44+
45+
### Commit Message Format
46+
47+
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
48+
format that includes a **type**, a **scope** and a **subject**:
49+
50+
```
51+
<type>(<scope>): <subject>
52+
<BLANK LINE>
53+
<body>
54+
<BLANK LINE>
55+
<footer>
56+
```
57+
58+
The **header** is mandatory and the **scope** of the header is optional.
59+
60+
Any line of the commit message cannot be longer 100 characters! This allows the message to be easier
61+
to read on GitHub as well as in various git tools.
62+
63+
The footer should contain a [closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.
64+
65+
Samples: (even more [samples](https://github.com/angular/angular/commits/master))
66+
67+
```
68+
docs(changelog): update changelog to beta.5
69+
```
70+
71+
```
72+
fix(release): need to depend on latest rxjs and zone.js
73+
74+
The version in our package.json gets copied to the one we publish, and users need the latest of these.
75+
```

‎ISSUE_TEMPLATE.md

+58
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
<!--
2+
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
3+
4+
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
5+
-->
6+
7+
## I'm submitting a...
8+
9+
<!-- Check one of the following options with "x" -->
10+
<pre><code>
11+
[ ] Regression (a behavior that used to work and stopped working in a new release)
12+
[ ] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
13+
[ ] Performance issue
14+
[ ] Feature request
15+
[ ] Documentation issue or request
16+
[ ] Support request
17+
[ ] Other... Please describe:
18+
</code></pre>
19+
20+
## Current behavior
21+
22+
<!-- Describe how the issue manifests. -->
23+
24+
## Expected behavior
25+
26+
<!-- Describe what the desired behavior would be. -->
27+
28+
## Minimal reproduction of the problem with instructions
29+
30+
For bug reports please provide the _STEPS TO REPRODUCE_ and if possible a _MINIMAL DEMO_ of the problem, for that you could use our [stackblitz example](https://stackblitz.com/edit/transloco-example)
31+
32+
## What is the motivation / use case for changing the behavior?
33+
34+
<!-- Describe the motivation or the concrete use case. -->
35+
36+
## Environment
37+
38+
<pre><code>
39+
Angular version: X.Y.Z
40+
<!-- Check whether this is still an issue in the most recent Angular version -->
41+
42+
Browser:
43+
- [ ] Chrome (desktop) version XX
44+
- [ ] Chrome (Android) version XX
45+
- [ ] Chrome (iOS) version XX
46+
- [ ] Firefox version XX
47+
- [ ] Safari (desktop) version XX
48+
- [ ] Safari (iOS) version XX
49+
- [ ] IE version XX
50+
- [ ] Edge version XX
51+
52+
For Tooling issues:
53+
- Node version: XX <!-- run `node --version` -->
54+
- Platform: <!-- Mac, Linux, Windows -->
55+
56+
Others:
57+
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
58+
</code></pre>

‎LICENSE

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

‎PULL_REQUEST_TEMPLATE.md

+43
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
## PR Checklist
2+
3+
Please check if your PR fulfills the following requirements:
4+
5+
- [ ] The commit message follows our guidelines: https://github.com/ngneat/transloco/blob/master/CONTRIBUTING.md#commit
6+
- [ ] Tests for the changes have been added (for bug fixes / features)
7+
- [ ] Docs have been added / updated (for bug fixes / features)
8+
9+
## PR Type
10+
11+
What kind of change does this PR introduce?
12+
13+
<!-- Please check the one that applies to this PR using "x". -->
14+
15+
```
16+
[ ] Bugfix
17+
[ ] Feature
18+
[ ] Code style update (formatting, local variables)
19+
[ ] Refactoring (no functional changes, no api changes)
20+
[ ] Build related changes
21+
[ ] CI related changes
22+
[ ] Documentation content changes
23+
[ ] Other... Please describe:
24+
```
25+
26+
## What is the current behavior?
27+
28+
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
29+
30+
Issue Number: N/A
31+
32+
## What is the new behavior?
33+
34+
## Does this PR introduce a breaking change?
35+
36+
```
37+
[ ] Yes
38+
[ ] No
39+
```
40+
41+
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
42+
43+
## Other information

0 commit comments

Comments
 (0)