send_game needs chat_id by ChatId not u32

[strongtu]

async fn message_handler(
    bot: Bot,
    msg: Message,
    me: Me,
) -> Result<(), Box<dyn Error + Send + Sync>> {
    println!("msg: {:?}", msg.text().unwrap_or("default"));

    let text = msg.text().unwrap_or("default");
    match text {
        "/game" => {
            bot.send_game( msg.chat.id.0,  "game_name")
                .reply_markup(make_game_message()).await?;
        }
        _ => {
            bot.send_message(msg.chat.id, text).await?;
        }
    }

    Ok(())
}

This will cause a compilation error because the chat_id type declared by send_game is u32, but the type of msg.chat.id is i64
and should change send_message(chat_id : u32) to send_message(chat_id : i64) to make it work

here is the issues detail #1065

[teloxidebot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @WaffleLapkin (or someone else) soon.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @teloxidebot author: the review is finished, PR author should check the comments and take action accordingly
• @teloxidebot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[syrtcevvi]

Hi!

Thank you for your pull request.

Our Requester trait is created by codegen, so I'm not sure that that change will be enough. I think, it worth to change the schema.ron in teloxide -core. So, the send_game will accept smth similar to send_message

[WaffleLapkin]

Thanks for noticing the mistake! We do have a dedicated ChatId type though, so you should use that.

[WaffleLapkin]

Suggested change

	ty: i64,
	ty: RawTy("ChatId"),