Tii
Tii
LOL I figured it out. It had something to do with xdebug. For another project I configured xdebug to show var_dump output with infinite depth: ``` xdebug.var_display_max_depth = -1 xdebug.var_display_max_children...
The problem still persists... :(
Just to be sure… you’re trying to do this in a private chat? „Available only in private chats between a user and the bot.“
does it work in a private chat?
We should think about a way to solve this. I think the current behaviour as described can get pretty frustrating.
Any idea? I don't like that different Update Types call something like ...Command... It is not a Command, it should not be called that way. Maybe we can change this...
I'm not sure what you're trying to achieve. Can you explain what problems you have and what you want to achieve?
@noplanman What do you think?
We have a few difficulties with finding the right way here, because you also can set a Guzzle Client yourself with `Request::setClient()` and this should always take precedence over custom...
Since we could add _Proposal 6_ without breaking anything that works now, that is my favorite for sure.