CRATEFIELD
Get started with Harness Join the waitlist

adapter-telegram

The TelegramBot port over the Telegram Bot API: send, edit and answer.

With cargo

cargo add cratefield-adapter-telegram
crates.iodocs.rsSource

What it is

adapter-telegram.

The TelegramBot port over the Telegram Bot API for the Cratefield harness. It speaks https://api.telegram.org/bot… through the runtime’s HttpClient port, verifies the webhook secret token on the way in, and maps Telegram’s own error codes rather than passing them through raw. Nothing about a chat’s authority is decided here; that is module-telegram’s, and it is where the rule about what a tap may finish lives.

From the crate’s own README.

Ports

Implements TelegramBot

History

Changelog.

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 2 versions recorded, newest first. Every published version is on crates.io.

  1. 0.1.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core

  2. 0.1.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-core

    Added

    • First release, 0.1.0: the TelegramBot port over the Telegram Bot API, through the HttpClient and Clock ports. It sends, edits and deletes messages and answers callback queries under global and per-chat rate budgets, parses typed inbound updates, and verifies the secret-token webhook. The bot token never rides a log line (#764).

One of 76 crates in the harness, all of them MIT and all of them in one repository.

Join the waitlist All modules