-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add sentry #589
Add sentry #589
Conversation
🦋 Changeset detectedLatest commit: 85585ef The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
5f29aef
to
37ab8fe
Compare
@@ -96,6 +97,7 @@ export const setSwapExecutionStateAtom = atom(null, (get, set) => { | |||
} | |||
}, | |||
onTransactionBroadcast: async (txInfo) => { | |||
setUser({ id: txInfo?.txHash }); |
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.
do we need this in addition to the other setUser with the source account address?
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.
yeah, we should keep both, one is setting id
and one is setting username
so both will be kept that way we have multiple ways of identifying the replay/session
@@ -304,6 +305,7 @@ export const SwapPage = () => { | |||
} | |||
setChainAddresses({}); | |||
setCurrentPage(Routes.SwapExecutionPage); | |||
setUser({ username: sourceAccount?.address }); |
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.
@ericHgorski we have two calls to setUser, the one to set address is here
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.
we should keep both, that way we have multiple ways of finding the replay
@@ -304,6 +305,7 @@ export const SwapPage = () => { | |||
} | |||
setChainAddresses({}); | |||
setCurrentPage(Routes.SwapExecutionPage); | |||
setUser({ username: sourceAccount?.address }); | |||
setSwapExecutionState(); |
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 also capture the route here
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.
how should i capture the route? as part of the user?
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.
not blocking the merge, we can use this https://docs.sentry.io/platforms/javascript/enriching-events/context/
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.
hmm, ok I'll test tags and contexts in a separate PR to decide which one to use
https://docs.sentry.io/platforms/javascript/enriching-events/tags/
https://docs.sentry.io/platforms/javascript/enriching-events/context/
Add sentry integration
Add session replay, auto recording when error occurs
Add messages for wallet connected/wallet disconnected