adding enum variant to handle unknown 400 #902
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.
Change Description
Created new ApiError enum variant to handle previously unhanded 400 error from Telegram. This was highlighted in issue #901. A new test case was added so the variant would be included in the "custom_result" test for the ApiError enum.
Doc Notes
The Doc Comment that was added to the variant tries to sum up the use case the error might occur however there is no official guidance on why this would occur so please change/add if we think of a better example of why this error might occur.
Tests ran and passed after change but please let me know if there are any other considerations 馃憤