Skip to content

Commit

Permalink
Initial commit
Browse files Browse the repository at this point in the history
  • Loading branch information
gjanco committed May 22, 2024
0 parents commit 7c87c46
Show file tree
Hide file tree
Showing 14 changed files with 1,063 additions and 0 deletions.
17 changes: 17 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# No Package Lock
package-lock.json

# No Temporary File
*.swp
.DS_Store

# No NPM Modules
node_modules

# No ZIP Files
*.zip

# No Testing Materials
data
generateData.js
.nyc*
153 changes: 153 additions & 0 deletions .tap/coverage/84632a4d-b0ed-46ac-b7c4-12f2758046c3.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,153 @@
{
"result": [
{
"scriptId": "640",
"url": "file:///Users/greg.janco/git/mezmo-cloudwatch/index.js",
"functions": [
{
"functionName": "",
"ranges": [
{
"startOffset": 0,
"endOffset": 3486,
"count": 1
}
],
"isBlockCoverage": true
},
{
"functionName": "getConfig",
"ranges": [
{
"startOffset": 695,
"endOffset": 1155,
"count": 2
},
{
"startOffset": 885,
"endOffset": 925,
"count": 1
},
{
"startOffset": 962,
"endOffset": 1136,
"count": 1
}
],
"isBlockCoverage": true
},
{
"functionName": "parseEvent",
"ranges": [
{
"startOffset": 1187,
"endOffset": 1296,
"count": 1
}
],
"isBlockCoverage": true
},
{
"functionName": "prepareLogs",
"ranges": [
{
"startOffset": 1334,
"endOffset": 2044,
"count": 2
}
],
"isBlockCoverage": true
},
{
"functionName": "",
"ranges": [
{
"startOffset": 1416,
"endOffset": 2041,
"count": 2
},
{
"startOffset": 1914,
"endOffset": 2016,
"count": 1
}
],
"isBlockCoverage": true
},
{
"functionName": "sendLine",
"ranges": [
{
"startOffset": 2063,
"endOffset": 3220,
"count": 2
},
{
"startOffset": 2207,
"endOffset": 3219,
"count": 0
}
],
"isBlockCoverage": true
},
{
"functionName": "interval",
"ranges": [
{
"startOffset": 2583,
"endOffset": 2671,
"count": 0
}
],
"isBlockCoverage": false
},
{
"functionName": "errorFilter",
"ranges": [
{
"startOffset": 2686,
"endOffset": 2796,
"count": 0
}
],
"isBlockCoverage": false
},
{
"functionName": "",
"ranges": [
{
"startOffset": 2802,
"endOffset": 3119,
"count": 0
}
],
"isBlockCoverage": false
},
{
"functionName": "",
"ranges": [
{
"startOffset": 3121,
"endOffset": 3217,
"count": 0
}
],
"isBlockCoverage": false
},
{
"functionName": "handler",
"ranges": [
{
"startOffset": 3238,
"endOffset": 3403,
"count": 0
}
],
"isBlockCoverage": false
}
]
}
],
"timestamp": 994434.773001,
"source-map-cache": {}
}
239 changes: 239 additions & 0 deletions .tap/processinfo/84632a4d-b0ed-46ac-b7c4-12f2758046c3.json

Large diffs are not rendered by default.

52 changes: 52 additions & 0 deletions .tap/test-results/test/index.js.tap
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
TAP version 14
# Subtest: test parseEvent with the sample test data described in README
ok 1 - should be equivalent
1..1
ok 1 - test parseEvent with the sample test data described in README # time=2.763ms

# Subtest: test getConfig
# Subtest: defaults
ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
ok 5 - should be equal
1..5
ok 1 - defaults # time=1.179ms

# Subtest: set key and raw event
ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
ok 5 - should be equal
1..5
ok 2 - set key and raw event # time=0.378ms

1..2
ok 2 - test getConfig # time=5.721ms

# Subtest: test prepareLogs
ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equivalent
ok 5 - should be equivalent
ok 6 - should be equal
ok 7 - should be equal
ok 8 - should be equal
ok 9 - should be equivalent
1..9
ok 3 - test prepareLogs # time=0.671ms

# Subtest: test sendLine
ok 1 - should be equal
1..1
ok 4 - test sendLine # time=0.148ms

# Subtest: test handler
ok 1 - should be equal
1..1
ok 5 - test handler # time=0.104ms

1..5
Empty file added CHANGELOG.md
Empty file.
138 changes: 138 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,138 @@
# Contributor's Code of Conduct

If you contribute to this repo, you agree to abide by this code of conduct for
this community.

We abide by the
[Contributor Covenant Code of Conduct, 2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/).
It is reproduced below for ease of use.

# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, religion, or sexual identity
and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
overall community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or
advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Community leaders 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, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
[[email protected]](mailto:[email protected]).
All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series
of actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or
permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within
the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available at
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder](https:/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at
https://www.contributor-covenant.org/translations.

15 changes: 15 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Contributing

## Github Workflow

Contributions are always welcome! Be sure to follow the [github workflow](https://guides.github.com/introduction/flow/) when contributing to this project:

* Create an issue, or comment on an issue to indicate what you are working on. This avoids work duplication.
* Fork the repository and clone to your local machine
* You should already be on the default branch `master` - if not, check it out (`git checkout master`)
* Create a new branch for your feature/fix `git checkout -b my-new-feature`)
* Write your feature/fix
* Stage the changed files for a commit (`git add .`)
* Commit your files with a *useful* commit message ([example](https:/Azure/azure-quickstart-templates/commit/53699fed9983d4adead63d9182566dec4b8430d4)) (`git commit`)
* Push your new branch to your GitHub Fork (`git push origin my-new-feature`)
* Visit this repository in GitHub and create a Pull Request.
Loading

0 comments on commit 7c87c46

Please sign in to comment.