Custom 'feedback_hook_url' per notification
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 887
- PR merge metrics
- No merged PRs in 30d
Description
Today we can only set a global '**feedback_hook_url**'.
However our application today is totally multi-client. Our API url is different depending on the user associated with the client, inside the same app.
Today you have the '**notif_id**' with send a unique string to identify the notification, but this require us to create a separate service on a global domain to filter the feedback and foward the to final service (on the client url, all the logic and connections do database and configs depends on the url subdomain attached to the client).
Please add a '**feedback_hook_url**' parameter to the notification too.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating how the global feedback_hook_url is configured and how notification parameters are represented, then trace where feedback requests are sent. Done means a notification can provide its own feedback_hook_url while existing global configuration continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100