Skip to content

Commit 686d5ec

Browse files
waterpleawaterplea
committed
initial commit
1 parent 261fe66 commit 686d5ec

Some content is hidden

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

76 files changed

+18692
-2
lines changed

‎.editorconfig

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Editor configuration, see https://editorconfig.org
2+
root = true
3+
4+
[*]
5+
charset = utf-8
6+
indent_style = space
7+
indent_size = 4
8+
insert_final_newline = true
9+
trim_trailing_whitespace = true
10+
11+
[*.md]
12+
max_line_length = off
13+
trim_trailing_whitespace = false

‎.github/CODEOWNERS

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# ==================================================================================
2+
# ==================================================================================
3+
# ng-event-filters codeowners
4+
# ==================================================================================
5+
# ==================================================================================
6+
#
7+
# Configuration of code ownership and review approvals for the angular/angular repo.
8+
#
9+
# More info: https://help.github.com/articles/about-codeowners/
10+
#
11+
12+
* @waterplea @MarsiBarsi
13+
# will be requested for review when someone opens a pull request

‎.github/ISSUE_TEMPLATE/bug_report.md

+32
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: 🐞 Bug report
3+
about: Create a report to help us improve
4+
title: '[BUG] '
5+
labels: ''
6+
---
7+
8+
# 🐞 Bug report
9+
10+
### Description
11+
12+
<!-- A clear and concise description of what the bug is -->
13+
14+
### Reproduction
15+
16+
<!-- Steps to reproduce or, preferably, a demo on StackBlitz or similar service -->
17+
18+
http://www.stackblitz.com/...
19+
20+
### Expected behavior
21+
22+
<!-- A clear and concise description of what you expected to happen -->
23+
24+
### Versions
25+
26+
- OS: [e.g. iOS]
27+
- Browser [e.g. chrome, safari]
28+
- Angular [e.g. 8]
29+
30+
### Additional context
31+
32+
<!-- Add any other context about the problem here -->

‎.github/ISSUE_TEMPLATE/feature_request.md

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

‎.github/PULL_REQUEST_TEMPLATE.md

+35
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
## PR Checklist
2+
3+
Please check if your PR fulfills the following requirements:
4+
5+
- [ ] The commit message follows [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0-beta.4/)
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+
- [ ] Bugfix
16+
- [ ] Feature
17+
- [ ] Refactoring (no functional changes, no api changes)
18+
- [ ] Other... Please describe:
19+
20+
## What is the current behavior?
21+
22+
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
23+
24+
Issue Number: N/A
25+
26+
## What is the new behavior?
27+
28+
## Does this PR introduce a breaking change?
29+
30+
- [ ] Yes
31+
- [ ] No
32+
33+
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
34+
35+
## Other information

‎.gitignore

+49
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# compiled schematics
2+
schematics/library-starter/*.js
3+
schematics/library-starter/*.js.map
4+
schematics/library-starter/*.d.ts
5+
6+
# compiled output
7+
/dist
8+
/tmp
9+
/out-tsc
10+
# Only exists if Bazel was run
11+
/bazel-out
12+
13+
# dependencies
14+
/node_modules
15+
16+
# profiling files
17+
chrome-profiler-events.json
18+
speed-measure-plugin.json
19+
20+
# IDEs and editors
21+
/.idea
22+
.project
23+
.classpath
24+
.c9/
25+
*.launch
26+
.settings/
27+
*.sublime-workspace
28+
29+
# IDE - VSCode
30+
.vscode/*
31+
!.vscode/settings.json
32+
!.vscode/tasks.json
33+
!.vscode/launch.json
34+
!.vscode/extensions.json
35+
.history/*
36+
37+
# misc
38+
/.sass-cache
39+
/connect.lock
40+
/coverage
41+
/libpeerconnection.log
42+
npm-debug.log
43+
yarn-error.log
44+
testem.log
45+
/typings
46+
47+
# System Files
48+
.DS_Store
49+
Thumbs.db

‎.travis.yml

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
language: node_js
2+
node_js:
3+
- "10"
4+
script:
5+
- npm run lint
6+
- npm run build
7+
- npm run test
8+
notifications:
9+
webhooks: https://coveralls.io/webhook

‎CHANGELOG.md

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Changelog
2+
3+
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

‎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

+32
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# Contributing
2+
3+
> Thank you for considering contributing to our project. Your help if very welcome!
4+
5+
When contributing, it's better to first discuss the change you wish to make via issue,
6+
email, or any other method with the owners of this repository before making a change.
7+
8+
All members of our community are expected to follow our [Code of Conduct](CODE_OF_CONDUCT.md).
9+
Please make sure you are welcoming and friendly in all of our spaces.
10+
11+
## Getting started
12+
13+
In order to make your contribution please make a fork of the repository. After you've pulled
14+
the code, follow these steps to kick start the development:
15+
16+
1. Run `npm ci` to install dependencies
17+
2. Run `npm start` to launch demo project where you could test your changes
18+
3. Use following commands to ensure code quality
19+
20+
```
21+
npm run lint
22+
npm run build
23+
npm run test
24+
```
25+
26+
## Pull Request Process
27+
28+
1. We follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0-beta.4/)
29+
in our commit messages, i.e. `feat(core): improve typing`
30+
2. Update [README.md](README.md) to reflect changes related to public API and everything relevant
31+
3. Make sure you cover all code changes with unit tests
32+
4. When you are ready, create Pull Request of your fork into original repository

0 commit comments

Comments
 (0)