New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
message.get_url() in chat with topics -> wrong url #1451
Labels
enhancement
Make it better!
Comments
Robotvasya
changed the title
message.get_url() in chat with topics
message.get_url() in chat with topics -> wrong url
Apr 6, 2024
Why don't you send a PR? Looks like it should be able to take both urls: within topic and within all group |
I'll send PR, no problem. I'm afraid that this behavior not only in this function but also remains somewhere else. |
Robotvasya
added a commit
to Robotvasya/aiogram
that referenced
this issue
Apr 8, 2024
9 tasks
Robotvasya
added a commit
to Robotvasya/aiogram
that referenced
this issue
Apr 8, 2024
Robotvasya
added a commit
to Robotvasya/aiogram
that referenced
this issue
Apr 9, 2024
Robotvasya
added a commit
to Robotvasya/aiogram
that referenced
this issue
Apr 10, 2024
Robotvasya
added a commit
to Robotvasya/aiogram
that referenced
this issue
Apr 10, 2024
Robotvasya
added a commit
to Robotvasya/aiogram
that referenced
this issue
Apr 10, 2024
Robotvasya
added a commit
to Robotvasya/aiogram
that referenced
this issue
Apr 12, 2024
Robotvasya
added a commit
to Robotvasya/aiogram
that referenced
this issue
Apr 23, 2024
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
aiogram version
3.x
Problem
The method message.get_url() returns wrong url when it call in chat with topics:
Returns
https://t.me/username/message_id
but shouldhttps://t.me/username/message_thread_id/message_id
aiogram/aiogram/types/message.py
Line 3750 in acf52f4
I have not checked whether there is such a problem in other methods of the Message object. And I haven’t checked whether this method is used in other parts of the aiogram framework.
Possible solution
possible patch
Alternatives
No response
Code example
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: