-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Allow for pattern matching empty inline queries #4817
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
Conversation
Could you add a test which checks that this works now? If you would like pointers where/how feel free to ask, here or in the dev chat. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the pr. I left a comment on the test below. please also
- have a look at the failing pre-commit run. Please run
pre-commit install
in your local clone to ensure the hooks run before the commit. see also our contrib guide. running black viapip install black && black .
should fix the current issues - add the file pointed out here. Use
bugfixes
instead ofother
. You can change the text to a more descriptive explanation. It will appear in the changelog.
Co-authored-by: Bibo-Joshi <22366557+Bibo-Joshi@users.noreply.github.com>
I've done about everything I knew how to do from your request. Please review and let me know if something is missing and how to fix it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for the contribution!
I just removed the line of code that prevents empty inline queries from being matched using the
pattern
parameter when creating an instance of anInlineQueryHandler
.update.inline_query
is assumed to always have thequery
property, which I can only assume is always the case, as theupdate.inline_query
object must not be None in this case anyway.Also added myself to AUTHORS.rst
I haven't modified any of the documentation as I feel like this changes makes the documentation more accurate, as the expected behavior is now in place.