-
-
Notifications
You must be signed in to change notification settings - Fork 206
feat: Client that uses Req. #946
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
cgarvis
wants to merge
1
commit into
getsentry:master
Choose a base branch
from
cgarvis:patch-1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+24
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| defmodule Sentry.ReqClient do | ||
| @behaviour Sentry.HTTPClient | ||
|
|
||
| @moduledoc """ | ||
| HTTP client for Sentry based on Req. | ||
|
|
||
| This client implements the `Sentry.HTTPClient` behaviour. | ||
| It's based on the [Req](https://github.com/wojtekmach/req) Elixir HTTP client, | ||
| which is an *optional dependency* of this library. If you wish to use another | ||
| HTTP client, you'll have to implement your own `Sentry.HTTPClient`. See the | ||
| documentation for `Sentry.HTTPClient` for more information. | ||
| """ | ||
|
|
||
| @impl true | ||
| def post(url, headers, body) do | ||
| case Req.post(url, headers: headers, body: body) do | ||
| {:ok, %{status: status, headers: headers, body: body}} -> | ||
| {:ok, status, headers, body} | ||
|
|
||
| {:error, error} -> | ||
| {:error, error} | ||
| end | ||
| end | ||
| end | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potential bug: The success case for
Req.postincorrectly pattern matches on a plain map (%{}) instead of the returned%Req.Response{}struct, which will cause aMatchError.Description: The
casestatement inSentry.ReqClientincorrectly pattern matches on a plain map,%{status: status, ...}, for the success case of aReq.postcall. According to theReqlibrary's documentation, successful calls return a struct,%Req.Response{...}. In Elixir, a struct will not match a plain map pattern. This mismatch will cause aMatchErrorto be raised for every successful HTTP request sent via this client, rendering it non-functional for its primary purpose of sending events to Sentry.Suggested fix: Update the pattern match in the
casestatement to expect a%Req.Response{}struct. Specifically, change the line{:ok, %{status: status, headers: headers, body: body}}to{:ok, %Req.Response{status: status, headers: headers, body: body}}.severity: 0.9, confidence: 1.0
Did we get this right? 👍 / 👎 to inform future reviews.