Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@process-engine/logging_api_contracts

Package Overview
Dependencies
Maintainers
8
Versions
104
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@process-engine/logging_api_contracts - npm Package Compare versions

Comparing version 1.0.2 to 1.0.3-8d77e1b4-b5

163

.github/ISSUE_TEMPLATE.md

@@ -1,27 +0,66 @@

#### Describe your issue
## BEFORE SUBMITTING
> Describe the issue or ask your question regarding this module.
> Provide as much relevant information as you can. If you're not sure if something
> is relevant or not, include it as well!
>
> Logs and screenshots are very welcome!
> **Please ensure you have followed this guide, _before_ submitting your issue!**
>
> - Check if this issue already exists (including closed issues!)
> - Prefix the issue title according to the [gitmoji guide](https://gitmoji.carloscuesta.me/)
> - Reference all PRs and issues related to this one
>
><details>
><summary>
>Click here for a list of commonly used issue emojis.
></summary>
>
>| Description | Glyphe | Emoji|
>|--------------------------|-----------------------------|------|
>| Bugfix | `:bug:` | 🐛 |
>| Fixing Security issues | `:lock:` | 🔒 |
>| Improving Performance | `:zap:` | ⚡️ |
>| New Feature | `:sparkles:` | ✨ |
>| Refactoring Code | `:recycle:` | ♻️ |
>| CI Pipeline related | `:construction_worker_man:` | 👷 |
>| Configuration releated | `:wrench:` | 🔧 |
>| Tests | `:white_check_mark:` | ✅ |
>| Removing Stuff | `:fire:` | 🔥 |
>| Dependencies Downgrade | `:arrow_down:` | ⬇️ |
>| Dependencies Upgrade | `:arrow_up:` | ⬆️ |
>| Linter | `:rotating_light:` | 🚨 |
>| Cosmetic | `:lipstick:` | 💄 |
>| Miscellaneous | `:package:` | 📦 |
>
></details>
>
> **Please remove this section when you're done creating this issue.**
#### How can others reproduce the issue?
## Description
> Describe your issue/question here.
>
> Provide as much relevant information as you can.
> If you're not sure if something is relevant or not, include it as well!
>
>**If this is a feature request, please give a short summary as to what you need it for!**
## Reproduction
> You can remove this section, if the issue isn't something that requires reproducton.
>
> Describe how others can reproduce this issue as precisely as possible.
>
>
> If you can't reproduce the issue, let us know what you tried!
>
> You can remove this section if the issue isn't something reproducable
> (for example for certain questions or feature requests).
>
> Logs, Screenshots and BPMN files are always helpful!
#### Possible solution
## Possible solution
> If you have a possible solution to this issue or an idea that might
> help us to find one, describe it here. Let us know what you tried!
> This section is usually only required when reporting bugs.
> So you can remove it, if this issue is not something that needs solving.
>
> You can remove this section if it'd be empty.
> Of course, if you make a feature request and already have an idea on how
> to implement it, you are welcome to describe your proposed solution here as well!
#### What's your setup
## My setup
> You can remove this section, if it's irrelevant to the issue
- OS (`Windows/OS X/Linux` + `version`):

@@ -31,93 +70,1 @@ - Node (`node --version`):

- Docker (`docker version --format '{{.Server.Version}}'`):
> You can remove this section if it's irrelevant to the issue
> (for example for certain questions or feature requests).
#### Issue checklist
Please check the boxes in this list after submitting your Issue:
- [ ] I've checked if this issue already exists
- [ ] I've included all the information that i think is relevant
- [ ] I've added logs and/or screenshots (if applicable)
- [ ] I've mentioned PRs and issues that relate to this one
## Example
<details>
<summary>
:warning: Before creating the issue, click here to expand and follow the guide.
</summary>
<br>
1. Be sure to fill out **every** topic presented in this template.
If a section is not valid or useful for your issue, feel free to remove it.
2. Use the attached Checklist to make sure your issue contains all relevant information.
3. Attach a label to your issue that reflects what your issue is all about.
**When your issue concerns only a specific platform, be sure to attach the label for that platform!**
4. Please use a fitting emoji at the beginning of your issue title.
Example 1 - Report a bug:
```md
:bug: Something is not working properly
```
Example 2 - Report a performance issue:
```md
:zap: Something is slower than it should be
```
Example 3 - Report a package vulnerability or security issue:
```md
:lock: Package xy produces vulnerabilites
```
```md
:lock: User XY has access to something he shouldn't have
```
Example 4 - Report missing test coverage:
```md
:white_check_mark: Add tests for...
```
You can of course phrase your titles however you like.
Just be sure they are short, to the point and convey the general idea of the issue you are experiencing.
</details>
## Emojis
<details>
<summary>
Expand for a list of most used Emojis.
</summary>
<br>
Please prefix your Issue with an Emoji.
Ref: https://gitmoji.carloscuesta.me/
| Description | Glyphe | Emoji |
|--------------------------|----------------------|--------|
| Bugfix | `:bug:` | 🐛 |
| Fixing Security Issues | `:lock:` | 🔒 |
| Configuration releated | `:wrench:` | 🔧 |
| Cosmetic | `:lipstick:` | 💄 |
| Dependencies Downgrade | `:arrow_down:` | ⬇️ |
| Dependencies Upgrade | `:arrow_up:` | ⬆️ |
| Formatting | `:art:` | 🎨 |
| Improving Performance | `:zap:` | ⚡️ |
| Initial commit | `:tada:` | 🎉 |
| Linter | `:rotating_light:` | 🚨 |
| Miscellaneous | `:package:` | 📦 |
| New Feature | `:sparkles:` | ✨ |
| Refactoring Code | `:recycle:` | ♻️ |
| Releasing / Version tags | `:bookmark:` | 🔖 |
| Removing Stuff | `:fire:` | 🔥 |
| Tests | `:white_check_mark:` | ✅ |
| Work In Progress (WIP) | `:construction:` | 🚧 |
</details>

@@ -1,17 +0,47 @@

:tada: **Thanks for submitting this Pull Request**
## BEFORE SUBMITTING
Please provide a list including your changes.
> **Please ensure you have followed this guide, _before_ submitting your PR!**
>
> - Prefix the PR title according to the [gitmoji guide](https://gitmoji.carloscuesta.me/).
> - Reference all PRs and issues relevant for this PR.
> - **Be sure that you have reviewed and tested every change you made here!**
> - If you're not sure how you can test your changes, don't hesitate to contact us!
> - List all fixed/closed issues here with `Closes #123` or `Fixes #123`.
> - **If no issue for this PR exists, please consider creating one!**
> - Of course, if this just fixes a typo, linter error or is something equally simple, no issue is required.
> - Add the number of this PR to this PRs body, so you can add it to the commit message.
> This will allow us to create a nice changelog for the next release.
>
><details>
><summary>
>Click here for a list of commonly used PR emojis.
></summary>
>
>| Description | Glyphe | Emoji|
>|--------------------------|-----------------------------|------|
>| Work In Progress (WIP) | `:construction:` | 🚧 |
>| Bugfix | `:bug:` | 🐛 |
>| Fixing Security Issues | `:lock:` | 🔒 |
>| Improving Performance | `:zap:` | ⚡️ |
>| New Feature | `:sparkles:` | ✨ |
>| Refactoring Code | `:recycle:` | ♻️ |
>| CI Pipeline related | `:construction_worker_man:` | 👷 |
>| Configuration releated | `:wrench:` | 🔧 |
>| Tests | `:white_check_mark:` | ✅ |
>| Removing Stuff | `:fire:` | 🔥 |
>| Releasing / Version tags | `:bookmark:` | 🔖 |
>| Dependencies Downgrade | `:arrow_down:` | ⬇️ |
>| Dependencies Upgrade | `:arrow_up:` | ⬆️ |
>| Initial commit | `:tada:` | 🎉 |
>| Linter | `:rotating_light:` | 🚨 |
>| Cosmetic | `:lipstick:` | 💄 |
>| Formatting | `:art:` | 🎨 |
>| Miscellaneous | `:package:` | 📦 |
>
></details>
>
> **Please remove this section when you're done creating this PR.**
To help us to create a meaningful Changelog, we agreed
to use an emoji-based commit-style. Use the [Emojis](#emojis)
we provided below.
## Changes
Fill out the following, provide reference to issues
and this PR- we will use this as merge commit message-body
and the title of this PR as commit-headline:
---
**Changes:**
1. Change 1

@@ -21,101 +51,10 @@ 2. Change 2

## Issues
**Issues:**
Closes #YourIssueNumber
Closes #Issue
Closes #Issue
Closes (...)
PR: #PullRequest
---
See the [examples](#example) for inspiration.
## How can others test the changes?
> Describe how others can test your changes (you can remove this section for typo fixes etc.)
## PR-Checklist
Please check the boxes in this list after submitting your PR:
- [x] You can merge this PR **right now** (if not, please prefix the title with "WIP: ")
- [x] I've tested **all** changes included in this PR.
- [x] I've also reviewed this PR myself before submitting (e.g. for scrambled letters, typos, etc.).
- [x] I've rebased the `develop` branch with my branch before finishing this PR.
- [x] I've **summarized all changes** in a list above.
- [x] I've mentioned all **PRs, which relate to this one**.
- [x] I've prefixed my Pull Request title is according to [gitmoji guide](https://gitmoji.carloscuesta.me/).
## Example
<details>
<summary>
:warning: Before merging please click here to expand and follow the guide.
</summary>
<br>
Please use `:twisted_rightwards_arrows:` at the beginning of your merge commit title.
Example 1:
<pre>
<code>
:twisted_rightwards_arrows: :bug: Fix Wrong Text Decoration at ...
</code>
</pre>
To get your commit message, just copy the first part of this pull request.
Example 2:
<pre>
<code>
**Changes:**
- Fixes Wrong Text Decoration at ...
- Fixes some typos
- ...
**Issues:**
Closes #NumberOfFixedIssue
PR: #NumberOfThisPR
</code>
</pre>
</details>
## Emojis
## How to test the changes
<details>
<summary>
Expand for a list of most used Emojis.
</summary>
<br>
Please prefix your commit messages with an Emoji.
Ref: https://gitmoji.carloscuesta.me/
| Description | Glyphe | Emoji |
|--------------------------|----------------------|--------|
| Bugfix | `:bug:` | 🐛 |
| Fixing Security Issues | `:lock:` | 🔒 |
| Configuration releated | `:wrench:` | 🔧 |
| Cosmetic | `:lipstick:` | 💄 |
| Dependencies Downgrade | `:arrow_down:` | ⬇️ |
| Dependencies Upgrade | `:arrow_up:` | ⬆️ |
| Formatting | `:art:` | 🎨 |
| Improving Performance | `:zap:` | ⚡️ |
| Initial commit | `:tada:` | 🎉 |
| Linter | `:rotating_light:` | 🚨 |
| Miscellaneous | `:package:` | 📦 |
| New Feature | `:sparkles:` | ✨ |
| Refactoring Code | `:recycle:` | ♻️ |
| Releasing / Version tags | `:bookmark:` | 🔖 |
| Removing Stuff | `:fire:` | 🔥 |
| Tests | `:white_check_mark:` | ✅ |
| Work In Progress (WIP) | `:construction:` | 🚧 |
</details>
> Describe how others can test your changes (not required when fixing typos, linter errors and such)
{
"name": "@process-engine/logging_api_contracts",
"version": "1.0.2",
"version": "1.0.3-8d77e1b4-b5",
"description": "the api-package for process-engine logging",

@@ -22,11 +22,11 @@ "main": "dist/commonjs/index.js",

"dependencies": {
"@essential-projects/iam_contracts": "~3.4.0"
"@essential-projects/iam_contracts": "^3.4.0",
"@types/express": "^4.16.0",
"@types/node": "^10.12.2"
},
"devDependencies": {
"@essential-projects/tslint-config": "^1.1.3",
"@types/express": "^4.16.0",
"@types/node": "^10.12.2",
"gulp": "^4.0.0",
"gulptraum": "^3.0.0",
"gulptraum-typescript": "^2.0.0",
"gulptraum-typescript": "^3.0.0",
"tsconfig": "^7.0.0",

@@ -33,0 +33,0 @@ "tslint": "^5.11.0",

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc