Explicit Sentry logging for error responses from the recipe search api #1694
+30
−11
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
fredex42
force-pushed
the
ag/report-searchapi-failures
branch
from
39cfb3f
to
0fb1db8
Compare
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.
What's changed?
Add explicit Sentry logging for error responses from the recipe search api.
If there are any transient issues with the search api, we need to know about them before we start trying to integrate to the main app. Since this is the only place it's in use at the moment, we want to get detailed information about any potential failures.
Implementation notes
n/a
Checklist
General
Relevant tests addedn/aClient
Screenshots / GIFs of relevant UI changes includedn/a