15 unstable releases (7 breaking)
0.8.0 | Nov 14, 2020 |
---|---|
0.7.0 | Mar 21, 2020 |
0.6.3 | Jul 17, 2019 |
0.6.1 | Feb 17, 2018 |
0.1.2 | Jul 30, 2015 |
#1599 in Web programming
801 downloads per month
Used in 7 crates
(6 directly)
255KB
6K
SLoC
Rust Telegram Bot Library
Documentation: | Latest crates.io version | master |
A library for writing your own Telegram bots. More information here. Official API here.
Example
Here is a simple example (see example/simple.rs
):
use std::env;
use futures::StreamExt;
use telegram_bot::*;
#[tokio::main]
async fn main() -> Result<(), Error> {
let token = env::var("TELEGRAM_BOT_TOKEN").expect("TELEGRAM_BOT_TOKEN not set");
let api = Api::new(token);
// Fetch new updates via long poll method
let mut stream = api.stream();
while let Some(update) = stream.next().await {
// If the received update contains a new message...
let update = update?;
if let UpdateKind::Message(message) = update.kind {
if let MessageKind::Text { ref data, .. } = message.kind {
// Print received text message to stdout.
println!("<{}>: {}", &message.from.first_name, data);
// Answer message with "Hi".
api.send(message.text_reply(format!(
"Hi, {}! You just wrote '{}'",
&message.from.first_name, data
)))
.await?;
}
}
}
Ok(())
}
You can find a bigger examples in the examples
.
Usage
This library is available via crates.io
. In order to use it, just add this to your Cargo.toml
:
telegram-bot = "0.7"
The library allows you to do E2E-testing of your bot easily: just specify TELEGRAM_API_URL
environment variable to point to your fake Telegram test server.
A lot of diagnostic information can be collected with tracing framework, see example/tracing.rs
).
Collaboration
Yes please! Every type of contribution is welcome: Create issues, hack some code or make suggestions. Don't know where to start? Good first issues are tagged with up for grab.
Dependencies
~11–24MB
~378K SLoC