Leandre Chamberland-Dozois
4c94a7c21e
fix: resolve TypeScript build errors in notification form types
2026-03-25 19:13:37 -04:00
LeC-D
40968c370b
refactor(notifications): hoist default values, remove else block in useNotificationForm
...
Per @ajhollid review: define defaults up-front with a NotificationDefaults type
and eliminate the trailing else branch entirely. The if/else-if blocks only
override when the type is matrix or telegram.
2026-03-25 18:06:26 -04:00
LeC-D and Claude Opus 4.6
a864bc0c05
fix: run format and fix build errors
...
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com >
2026-03-25 16:52:48 -04:00
LeC-D
fe242b1977
fix: replace nested ternaries and remove type casts per review
...
- useNotificationForm: replace nested ternary with if/else if/else block
- TelegramProvider: type error as unknown and access properties safely
via instanceof checks instead of casting to HTTPError
2026-03-25 14:03:49 -04:00
Léo
eacbb227c3
feat(notifications): add Telegram notification channel ( #2753 )
...
Add Telegram as a new notification type, allowing users to receive
monitor alerts via a Telegram bot.
Configuration requires:
- Bot token (obtained from @BotFather)
- Chat ID (user, group, or channel)
Changes:
- TelegramProvider: sends HTML-formatted messages via Telegram Bot API
- NotificationsService: route telegram type to TelegramProvider
- Notification model/types: add 'telegram' to NotificationChannel enum
- Server validation: telegram schema (accessToken + address/chat_id)
- Client Types/Validation: telegram schema with accessToken + address
- useNotificationForm: handle telegram defaults
- Notifications create page: render Telegram config UI
- en.json: add telegram i18n keys
2026-03-24 10:15:46 -04:00
Alex Holliday
0b5e28c296
form
2026-01-29 19:29:36 +00:00