Repository navigation
Conversation
Explain how to read the message, HTTP status and body from a raised Typesense::Error, which class each status code maps to, and that network errors are re-raised as-is once retries run out.
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.
Adds an "Error handling" section to the README. This is the README part of #60, split out on its own.
It also corrects the example from #60. Errors are built with
new(response: response), soe.datais a Hash and the Faraday response is ate.data[:response]. The #60 example callede.data.status, which raisesNoMethodError.Changes
Typesense::Error.Errnoexception, not as aTypesense::Error.Verification
Ran the README example against
masterwith a stubbed 404 response:e.messageis"Not Found",e.data[:response].statusis404, ande.data[:response].bodyis the raw JSON body.PR Checklist