You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a bit inexperienced with the Telegram API, and this is the kind of moment I wish the documentation would be a bit beefier around these details. Instinctively, it would make more sense to me if the conversation held the chat Id with the user. I need to understand why this was not implemented this way.
Let me know if you need any more details
Thank you for your amazing work
The text was updated successfully, but these errors were encountered:
I have a doubt about the way chat IDs are handled in Nutgram, for which I could not find an answer.
I created an inline menu, the running method is polling, here is a snippet of a handler's code:
What's the difference between the Bot Chat ID and the Conversation Chat ID?
How come the bot holds the chat ID and the InlineMenu holds NULL?
When does an InlineMenu hold a Chat ID?
Will the bot always be reliable with Chat IDs with multiple concurrent users?
According to this documentation: https://nutgram.dev/docs/usage/conversations#starting-a-conversation-from-server-side , I should be able to retrieve the chat ID from
$this
since InlineMenu extends ConversationI am a bit inexperienced with the Telegram API, and this is the kind of moment I wish the documentation would be a bit beefier around these details. Instinctively, it would make more sense to me if the conversation held the chat Id with the user. I need to understand why this was not implemented this way.
Let me know if you need any more details
Thank you for your amazing work
The text was updated successfully, but these errors were encountered: