Notifications should use names instead of IDs #45

Closed
opened 2 years ago by t_aus_m · 1 comments
t_aus_m commented 2 years ago

When I'm getting a notification via Gotify, it currently uses the IDs instead of the names for generating the headline of the notification.

[OK] /2Pingcheck/Home/ping (previously CRITICAL)

Where in my case the ID of the group is 2Pingcheck and the name would be Ping.

In my oppinion, gotify should use the names, as declaring them would be rather useless otherwise.

When I'm getting a notification via Gotify, it currently uses the IDs instead of the names for generating the headline of the notification. ``` [OK] /2Pingcheck/Home/ping (previously CRITICAL) ``` Where in my case the ID of the group is `2Pingcheck` and the name would be `Ping`. In my oppinion, gotify should use the names, as declaring them would be rather useless otherwise.
Owner

You're right with that - I'll probably be using "Ping-Check » Home » Ping" as a syntax for name-based paths in notifications. The IDs should be mostly used for the API and internally (e.g. for overriding checks and so on).

You're right with that - I'll probably be using "Ping-Check » Home » Ping" as a syntax for name-based paths in notifications. The IDs should be mostly used for the API and internally (e.g. for overriding checks and so on).
momar closed this issue 2 years ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.