Yoel Navas E.
Yoel Navas E.
So, if we do: ``` ... ctx = await conversation.waitFor( , (ctx) => ctx.message?.text === "/cancel" && conversation.halt() ); ... ``` What happens to this update? Does it get dropped?...
Yup! LGTM
Or maybe consuming the update should be the default, as you said; then you need to specify `drop: false` to give back control to the middleware system?
Setting defaults to `true` in these cases feels more natural to me, but I agree with you, they should be consistent between the two. I'm ok with either one, true...
Yo, I have been very busy with work. What's the status of this one? Is there something that needs to be tested/reviewed?
> I can imagine that it is desirable to have a timeout that regard **each wait call** individually, rather than seeing the conversation in its entirety. Should this be changed...
I'm wondering how will this work on serverless environments that scale to cero, like cloud functions. What would happen if the instance (or function) handling this convo goes to sleep...
Same issue here with VSCode auto-complete; I thought for a moment that VSCode was broken