- 
          
- 
        Couldn't load subscription status. 
- Fork 1.7k
ref(v8): Remove Transaction concept #11422
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
Conversation
| size-limit report 📦
 | 
e27da11    to
    7b355d0      
    Compare
  
    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.
Lets goooooo
|  | ||
| export type AugmentedNextApiResponse = NextApiResponse & { | ||
| __sentryTransaction?: Transaction; | ||
| __sentryTransaction?: SentrySpan; | 
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.
I think we can remove this, nothing seems to use __sentryTransaction
| // In all other cases, use the request's associated transaction (if any) to overwrite the event's `transaction` | ||
| // value with a high-quality one | ||
| const reqWithTransaction = req as { _sentryTransaction?: Transaction }; | ||
| const reqWithTransaction = req as { _sentryTransaction?: Span }; | 
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.
Nothing seems to set _sentryTransaction 🤔
Can we remove all of this functionality here?
This removes the `Transaction` class and any user facing remainders of this. Now, we just always create a `SentrySpan` class, and this class handles sending the transaction event when it is a root span.
This removes the
Transactionclass and any user facing remainders of this.Now, we just always create a
SentrySpanclass, and this class handles sending the transaction event when it is a root span.