Print errors from action handlers in stdout instead of ignoring them #197
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
telegram-bot-simple
Right now
liftClientMinside action handler,This PR prints Telegram Bot API errors in stdout in the same way as with parser errors for incoming updates instead of silently ignoring them.
For now
liftClientMdocumentation updated. Unfortunately, Telegram Bot API does not provide error status code that could be easily modelled intelegram-bot-api. As far as I see, it is a subject of reverse-engineering (example: https://github.com/TelegramBotAPI/errors). We will think about the better way of dealing with such issues.