ref(transports): Add back client reports #4998
Closed
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.
This PR mainly aims to add back client reports to the SDK using the new transports:
Contents
transport.send()
returnvoid
instead of response information. We do not need that information.DropReason
type to use in place ofOutcome
to be more in line with our docs. Outcome is a very overloaded term.Outcome
now describes an "outcome object" like the docs use the term:Response
,EventStatus
,SentryRequestType
,SentryRequest
types - were not needed anymoreDataCategory
type in favor ofTransportCategory
to be more in line with the docs. We use it for client outcome categories and rate limit categories.EnvelopeItemType
type.envelopeItemTypeToDataCategory
to map from envelope item types to data categories. This mapping is taken from the python SDK.eventStatusFromHttpCode
function. It is not needed anymore.