docs: update README for Slack/Telegram adapters#18
Conversation
Covers adapter-owned routing (Approach A), message formatting, rate limits, breaking changes to RoutingConfig/FormattedAlert, and migration path from global routing to per-adapter config. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ting - Quick Start shows all three adapters (Discord, Slack, Telegram) - Multi-Channel Routing updated to adapter-owned config pattern - Per-Environment Config removes deprecated pings field - Full Configuration removes global routing section - Adapters table marks Slack and Telegram as built-in Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Code Review
This pull request updates the documentation to reflect that Slack and Telegram adapters are now built-in. It also documents the transition from a global routing configuration to a per-adapter routing model, providing updated examples for Discord, Slack, and Telegram. A suggestion was made to clarify that the mentions property expects an array of strings for better alignment with the underlying type definitions.
| webhookUrl: '...', | ||
| channels: {}, // level → webhook URL | ||
| tags: {}, // tag → webhook URL | ||
| mentions: {}, // level → mention strings |
There was a problem hiding this comment.
The comment level → mention strings is slightly ambiguous. Since the mentions property in DiscordAdapterOptions (and other adapters) is typed as Partial<Record<AlertLevel, string[]>>, it would be clearer to specify that it expects an array of strings, as shown in the examples above.
| mentions: {}, // level → mention strings | |
| mentions: {}, // level → string[] (mentions) |
References
- The AlertLevel type for warnings is 'warning', which is distinct from the API method name .warn().
Summary
channels/tags/mentionspatternpingsfrom per-environment config examplesroutingfrom full configuration referenceFollows up on #16.
🤖 Generated with Claude Code