mirror of
https://github.com/teloxide/teloxide.git
synced 2024-12-22 14:35:36 +01:00
53be9d0e92
In reordering the parameters, I stick the following principle: place parameters from least changing to most changing. Thus, we have config and bot right from the beginning, next a dialogue with a possible payload, and next updates such as messages, inline queries, etc. This principle is used in languages with a native support for currying, although in Rust people appear to order parameters arbitrarily, so this commit is mostly for the sake of consistency.
Former-commit-id: 5922984f6c
64 lines
2.7 KiB
Rust
64 lines
2.7 KiB
Rust
use teloxide::{
|
|
prelude::*,
|
|
types::{
|
|
InlineQueryResult, InlineQueryResultArticle, InputMessageContent, InputMessageContentText,
|
|
},
|
|
Bot,
|
|
};
|
|
|
|
#[tokio::main]
|
|
async fn main() {
|
|
pretty_env_logger::init();
|
|
log::info!("Starting inline bot...");
|
|
|
|
let bot = Bot::from_env();
|
|
|
|
let handler = Update::filter_inline_query().branch(dptree::endpoint(
|
|
|bot: Bot, q: InlineQuery| async move {
|
|
// First, create your actual response
|
|
let google_search = InlineQueryResultArticle::new(
|
|
// Each item needs a unique ID, as well as the response container for the
|
|
// items. These can be whatever, as long as they don't
|
|
// conflict.
|
|
"01".to_string(),
|
|
// What the user will actually see
|
|
"Google Search",
|
|
// What message will be sent when clicked/tapped
|
|
InputMessageContent::Text(InputMessageContentText::new(format!(
|
|
"https://www.google.com/search?q={}",
|
|
q.query,
|
|
))),
|
|
);
|
|
// While constructing them from the struct itself is possible, it is preferred
|
|
// to use the builder pattern if you wish to add more
|
|
// information to your result. Please refer to the documentation
|
|
// for more detailed information about each field. https://docs.rs/teloxide/latest/teloxide/types/struct.InlineQueryResultArticle.html
|
|
let ddg_search = InlineQueryResultArticle::new(
|
|
"02".to_string(),
|
|
"DuckDuckGo Search".to_string(),
|
|
InputMessageContent::Text(InputMessageContentText::new(format!(
|
|
"https://duckduckgo.com/?q={}",
|
|
q.query
|
|
))),
|
|
)
|
|
.description("DuckDuckGo Search")
|
|
.thumb_url("https://duckduckgo.com/assets/logo_header.v108.png".parse().unwrap())
|
|
.url("https://duckduckgo.com/about".parse().unwrap()); // Note: This is the url that will open if they click the thumbnail
|
|
|
|
let results = vec![
|
|
InlineQueryResult::Article(google_search),
|
|
InlineQueryResult::Article(ddg_search),
|
|
];
|
|
|
|
// Send it off! One thing to note -- the ID we use here must be of the query
|
|
// we're responding to.
|
|
let response = bot.answer_inline_query(&q.id, results).send().await;
|
|
if let Err(err) = response {
|
|
log::error!("Error in handler: {:?}", err);
|
|
}
|
|
respond(())
|
|
},
|
|
));
|
|
|
|
Dispatcher::builder(bot, handler).enable_ctrlc_handler().build().dispatch().await;
|
|
}
|