More flexible logging options about telegram-bot-api HOT 7 CLOSED

What would you suggest doing? A chan for errors?

Is there anywhere else this is an issue besides UpdateChan?

from telegram-bot-api.

I've been trying to work out what the most idiomatic pattern would be for this, but have come up short so far sadly.

Perhaps a log interface then a logger instance can be passed in (either the standard golang logger, or any of the other loggers that implement identical methods)?

from telegram-bot-api.

I wonder if it wouldn't just be easier to implement the function in your own code, considering the entire thing is 18 lines of code.

from telegram-bot-api.

hmm point, I had kind of expected it to rely on internal functions but it seems it doesn't.

If the functions used by it are considered public and not likely to change to private, then that does seem like a decent option in this case!

from telegram-bot-api.

All it's doing is looping a call to BotAPI.GetUpdates, which is always going to stay public.

I'm going to close this issue. If anyone has suggestions later, feel free to mention them and I'll reopen it!

from telegram-bot-api.

@Syfaro maybe we can use logrus instead log pkg because logrus offer a lot of logging layers (panic, debug, info, error, fatal, etc).

from telegram-bot-api.

I am having this problem too. I am using Uber's zap, with jsonl format. The internal logger keep printing out logs, e.g getUpdates resp:/req.
Of course those lines are not use anyway, but maybe in the future I would like to collect those logs too, so it needs to be configurable.

from telegram-bot-api.