feat: notification types (success, failed) / rework
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
For example for database backup, there is only an on and off switch for the notification, but it notifies you when the backup was successfully created and when it fails. It would be great to have an option to only get notified when the backup fails. This would be extremely useful for notification priorities and to set them for every notification option.
Describe the solution you'd like
I will explain it in the PR
Describe alternatives you've considered
x
Additional context
No response
Will you send a PR to implement it?
No, but yes when it is not implemented until July / August where I have time to do that
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing notification settings and database backup notification flow. The issue requests separate success and failure notification controls, with priorities available for each notification option. Done means users can choose which outcomes trigger notifications and configure their priorities, but the implementation location and acceptance details are left for the proposed PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100