From d3f478e42a93e9e3decb7380d6dac59e0887246b Mon Sep 17 00:00:00 2001 From: Jasmin Bom Date: Thu, 14 Feb 2019 12:12:56 +0100 Subject: [PATCH] Updated Transition guide to Version 12.0 (markdown) --- Transition-guide-to-Version-12.0.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Transition-guide-to-Version-12.0.md b/Transition-guide-to-Version-12.0.md index 851b934..3d62a9c 100644 --- a/Transition-guide-to-Version-12.0.md +++ b/Transition-guide-to-Version-12.0.md @@ -11,6 +11,7 @@ * [CommandHandler](#commandhandler) * [PrefixHandler](#prefixhandler) * [MessageHandler](#messagehandler) + * [ConversationHandler](#conversationhandler) * [Filters in handlers](#filters-in-handlers) * [Special note about regex filters](#special-note-about-regex-filters) @@ -115,6 +116,10 @@ Newly added is the `PrefixHandler`. [read the docs ](https://python-telegram-bot `RegexHandler` is being deprecated. It's basically a MessageHandler with a `Filters.regex`, now the CallbackContext contains all match information. For now we keep it in, but you should switch the use of `RegexHandler` to using `MessageHandler(Filters.regex('pattern'), callback)`. See [Special note about regex filters](#special-note-about-regex-filters) and [Note about group and groupdict](#note-about-group-and-groupdict) for more details. +## ConversationHandler +The arguments `run_async_timeout` and `timed_out_behavior` have been removed. +The timeout for waiting for a @run_async handler is now always 0. If an update would have waited before, ConversationHandler will now try to use a handler in the new special state `ConversationHandler.WAITING`. This allows you to either manually wait in the handler if you want the old functionality, or send a message back to the user like "I am still processing your last request, please wait". + *** # Filters in handlers Using a list of filters in a handler like below has been deprecated for a while now. Version 12 removes the ability completely.