Here you go :wink:
import canoe.api._
import canoe.api.models.Keyboard
import canoe.models.{CallbackButtonSelected, InlineKeyboardButton, InlineKeyboardMarkup, Update}
import canoe.syntax._
import cats.Monad
import cats.effect.concurrent.Ref
import cats.effect.{Concurrent, ExitCode, IO, IOApp}
import cats.implicits._
import fs2.{Pipe, Stream}
Can't find this method
Are you using laterst version
0.5.0?
that's something that could be added to
Scenario though
if you're interested, you can raise an issue in the project and I'll find some time to work on it soon
:wink:
Cause I don't see any method with loginUrl
InlineKeyboardButton constructor methods don't expose this param, my bad
I'll get back to you later today with this
this is an easy one, just another constructor method in
InlineKeyboardButton companion object with some description
@augustjune Hey wanted to say thank you for the last update, really helped. Could you also check my issue. Maybe you remember about being able to call scenarios in callbacks? augustjune/canoe#218
Hi @augustjune and thanks for the library :)
a quick question: i'm developing a bot with different scenarios and callbacks and was wondering if there are any way to have a "global exception handler" instead of use .attempt or .handleErrorWith for each of the scenarios.
i was expecting the app not to crash if something fails during the evaluation of one of the scenarios (because of a bad input, some unhandled edge case, temporary connection error with external sources, telegram server not responding ..).
i'have tried to use the handleErrorWith/attempt in the main stream:
telegramClient
.flatMap(implicit client =>
Bot
.polling[IO]
.follow(scen1,scen2,scen3)
.through(callback1)
//tried here
)
//tried here
.compile
.drain
.as(ExitCode.Success)but the underlying stream seems to explode:
[ioapp-compute-3] INFO o.h.c.PoolManager - Shutting down connection pool: curAllocated=1 idleQueues.size=1 waitQueue.size=0 maxWaitQueueLimit=256 closed=false
Non-daemon threads currently preventing JVM termination: - 29: Thread[pool-1-thread-1,5,main]
- - 44: Thread[DestroyJavaVM,5,main]Am i missing something?
Hi @augustjune !! I´m CS student and a few folks and me are using canoe for a development course project. I´m trying to manage inline queries but I can't quite find the way...Could you give me any hint?
Lot of thanks for your work, it's my first time dealing with cats and this way is being enlightening for me. :clap:
Lot of thanks for your work, it's my first time dealing with cats and this way is being enlightening for me. :clap:
@balath I'm so glad to hear that you're using this lib for your course project. I'll be happy to help if you guys have any issues or want-to-know-hows along your way :wink:
2 replies
I separate them because in the first case you might want to drive the behaviour of your bot depending on user input, e.g. correcting the user , providing a set of viable options and continuing the scenario. see:
.tolerate and .cancel methods that you can use to steer the flow
for the second type of errors (underlying communication errors / errors in your business layer or canoe itself), you can handle them on the top level as you've described and restart the whole bot if such an error occurred