Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Get DTO #757

Unanswered
ilyazastrognov asked this question in Q&A
Feb 25, 2026 · 2 comments · 1 reply
Discussion options

Hello,

I have been struggling with your Telegraph package for the second day now.
In your documentation (https://docs.defstudio.it/telegraph/v1/features/dto
), there is information about data received from the request wrapped into DTOs. How can I access these DTOs?

I have tried different approaches and went through the entire codebase of your project, but I still couldn’t understand where the public methods that return these DTOs are located.
At the moment, I am forced to work directly with the request.

I am really looking forward to your response. Thank you!

You must be logged in to vote

Replies: 2 comments 1 reply

Comment options

the DTOs belongs to a received message through a webhook or a manual polling

for example here:

image
You must be logged in to vote
1 reply
Comment options

But there is no update_id in the message

Comment options

Yes, I know that — I probably didn’t clarify my question properly.

I’m interested in TelegramUpdate, specifically update_id.

The problem I’m trying to solve is that Telegram often sends duplicate messages if the success response doesn’t arrive immediately. I’m receiving a huge number of incoming messages per second from the bot, and this happens quite often. My flow is Redis -> SceneManager -> Job -> Notificator.

So I absolutely need a way to check something like:

$this->message->updateId != $cache->getKey('update_id')->from('telegram_id')

Also, in:

protected function handleCallbackQuery(): void
{
 $this->callbackQuery->data()->updateId
}

there is no update_id either.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
Converted from issue

This discussion was converted from issue #756 on February 25, 2026 07:22.

AltStyle によって変換されたページ (->オリジナル) /