feat: add TelegramEx.Error struct for API errors#23
Merged
Conversation
Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
Owner
|
Thanks for your contribution! Truly appreciated. 👏 |
This file contains hidden or 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.
Description
Adds a
TelegramEx.Errorstruct so API errors surface their code, description, and retry hint instead of collapsing to a single:bad_requestatom.TelegramEx.APInow returns{:error, %TelegramEx.Error{}}from both error-handling paths (get_updates/2and the sharedhandle_response/1), parsingerror_code,description, andparameters.retry_afterfrom the response body and keeping the raw payload around. This makes it possible to, for example, readretry_afteron a 429 and back off appropriately.Ready Checklist
mix testpasses locally/exampleRelated Issues
Closes #19