sourcefuse / loopback4-notifications Goto Github PK

node-apn/node-apn#700

Please update use of this, It has been unmaintained since 2019 and is vulnerable

Describe the bug
Incorrect package used in documentation, instead of loopback-notifications/ses, it must be loopback4-notifications/ses

Screenshots

Is your feature request related to a problem? Please describe.
Node v14 reaching its end of life this month. Loopback removes support for node v14 in all of its packages we depend on.

Sourceloop packages/services also currently have v12 and v14 as the supported versions.

Describe the solution you'd like
Remove the support for node v14 and v12. And add the support for the latest LTS version v18.

Describe alternatives you've considered
__

Additional context
__

Describe the bug
remove all current vilnenrability of loopback4-notifications.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
Copy the Readme to root as well

Is your feature request related to a problem? Please describe.
Adding semantic release for automatic release of packages.

Describe the solution you'd like
Using npm semantic-release

Describe alternatives you've considered

Additional context

Is your feature request related to a problem? Please describe.
There should be a way to send notifications through APNS.

Describe the solution you'd like
Can create a new provided similar to the FCM provider, using the node-apn or any other equivalent library to send notifications through APNS.

Additional context
There is already a way to send APNS based notifications using Pubnub but that requires Pubnub, there should be an independent way to send such notifications like there is for FCM based notifications.

Describe the bug
Loopback version update

Describe the bug
After installing the package and running the project, it says 'aws-sdk' is missing.

To Reproduce
Steps to reproduce the behavior:

1. Install the 'loopback4-notifications' package.
2. Follow the readme usage steps for Pubnub notifications.
3. Run the application.
4. It throws an error saying 'aws-sdk' is required.

Expected behavior
It should not ask to install 'aws-sdk' when I don't need it.

• update all dependencies ( including dev and peer dependencies)
• use node version 16 for the same

Is your feature request related to a problem? Please describe.
After the sourceloop release processes regression on jenkins the release of packages needs to be done locally.

Describe the solution you'd like
Set up a manually dispatch-able github action to publish releases.

Describe alternatives you've considered
The possible alternate is to publish packages locally but that requires keeping the credentials environment already setup.

Additional context
__

Describe the bug

• Loopback version update

Describe the bug
Version bump for release

Describe the bug
Loopback version updates

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.

1. Remove support for node 16 and lower versions
2. update package deps.

Describe the solution you'd like
Changes in the node property of package.json
This will be a breaking change.

Describe the bug
loopback version update

Describe the bug
Currently the issues and PR never closed even if inactive.
They should be closed automatically.

To Reproduce
Steps to reproduce the behavior:

1. Create a new issue/Pr
2. Observe it.
3. Even after no activity it stays open.

Expected behavior
Inactive issues/Pr should be closed automatically.

Describe the bug
This issue is supposed to be used for all deps update and chore PRs.

Describe the bug
Fix sonar quality gate issues

Screenshots
If applicable, add screenshots to help explain your problem.

https://sonarcloud.io/project/issues?resolved=false&types=CODE_SMELL&id=sourcefuse_loopback4-notifications

Is your feature request related to a problem? Please describe.
Need to send SMS via twilio

Describe the solution you'd like
Twilio as a provider for SMS

Describe alternatives you've considered
AWS SNS is not a good option for SMS as its delivery is unreliable

Additional context
Add any other context or screenshots about the feature request here.

Describe the bug
Add sonar and synk badges

Describe the bug
fixing mock-sdk in unit test

Describe the bug
Update lb4 dependencies in the package

For further information refer to the link below:
sourcefuse/loopback4-soft-delete#197

To have a consistent header in all sourceloop packages.
Reference readme: https://www.npmjs.com/package/@sourceloop/cache

Describe the bug
loopback version update

Describe the bug
The PR template is missing in this repo

To Reproduce
When we create a PR no template is used

Expected behavior
There should be a PR template

Describe the bug
to use PushNotification, we need to import it like :

import {PushNotification} from 'loopback4-notifications/dist/providers/push/index';

Expected behavior
It must be like :
import {PushNotification} from 'loopback4-notifications/push'

Describe the bug
When trying to send SMS I am getting this error

To Reproduce
Follow the steps in the documentation of this repository. Include the required keys and region in .env file.

code
await this.notificationProvider.publish({ body: 'OTP:' + authOtp.otp, receiver: {to: [{id: '9876543210/*replaced the actual phone number*/'}]}, sentDate: new Date(), type: MessageType.SMS }).catch(smsError => { console.log(smsError); });

Expected behavior
No error.

Screenshots

Additional context

Describe the bug

• License and Copyright Headers’ Year Upgradation

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Can use configurable firebase notification payload object instead of data payload only

Please check the different type of payloads
https://firebase.google.com/docs/cloud-messaging/concept-options

Additional Context -

the fcm-provider has a similar functionality already Implemented, the fcm-provided can refactor and reuse that same code to provide this in the pubnub notification provided.

Is your feature request related to a problem? Please describe.
After the release process has been moved to github action changelog is not being generated.

Describe the solution you'd like
Invoke the release notes js file for changelog generation.

Describe alternatives you've considered
Using the same approach as used during jenkins release process

Describe the bug
Test case coverage missing and not up to the mark

To Reproduce
We should have at least 75% unit test case coverage for this package.

Describe the bug
Right now Issue description is not visible in the changelog
To Reproduce
Steps to reproduce the behavior:

1. Release a new version
2. check the changelog
3. Issue Description not visible
4. Issue link not clickable

Describe the bug
Changes for semantic-release
when dependencies are updated with chore type new version is not released

To Reproduce
try updating the dependencies using chore(deps)

Expected behavior
when dependencies are updated with chore type new version must be released

Describe the bug
Loopback version updates.

Is your feature request related to a problem? Please describe.
Right now the changelog created for releases is not well in detail and informative.
Request to generate detailed changelog.

Describe the solution you'd like
Can use different npm packages available

See: sourcefuse/arc-docs#26