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
The way to provide the optional parameter, similar to how javascript would need it requires the use of Protocol, the Callable interface is not sufficient.
As it is, the typing says that you require to provide a turn_context to logic, but if you provide it, the function call_next_middleware breaks.
To solve this I am not sure what is the best approach, but as an initial point, could this be added? so at least if you send a turn_context it doesn't throw an error?
@alexrecuenco - Thank you for your patience. Can you provide more information on what it is you are trying to do? Are you trying to utilize a middleware option, like ShowTypingMiddleware, and are experiencing the problem then?
Are you able to include any code I can test with?
stevkan
added
the
bug
Indicates an unexpected problem or an unintended behavior.
label
May 2, 2025
https://github.com/microsoft/botbuilder-python/blob/13ee2f25ec3b7470fc4f570d7624b59487a98d38/libraries/botbuilder-core/botbuilder/core/middleware_set.py#L74C1-L75C1
The way to provide the optional parameter, similar to how javascript would need it requires the use of Protocol, the Callable interface is not sufficient.
As it is, the typing says that you require to provide a turn_context to logic, but if you provide it, the function call_next_middleware breaks.
To solve this I am not sure what is the best approach, but as an initial point, could this be added? so at least if you send a turn_context it doesn't throw an error?
Otherwise, can that parameter, turnContext, be removed?
The text was updated successfully, but these errors were encountered: