mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Add html body support for Telegram Notification #3208
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3208
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wvolkov on GitHub (Mar 20, 2024).
📑 I have found these related issues/pull requests
I haven't found anything related to Telegram html body support among current opened issues.
🏷️ Feature Request Type
Change to existing notification-provider
🔖 Feature description
It would be great to add option of rich html support while posting messages to TG bot api for more convenient view of nearly-add code-foramtting support at telegram.
✔️ Solution
Add toggle to TG client to support HTML and then pass to body that flag:
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Mar 20, 2024):
FYI:
If we can make the telegram notification provider have "cards" instead of simple text-messages, I don't think this needs a toggle in the notifications.
See https://github.com/louislam/uptime-kuma/pull/4538 for what I mean with cards.
Doing such detaileded work with notification providers is sadly not something that the core team can do for time reasons.
=> we rely on contributions from users of said notification provider, which know what is possible using said provider.