Skip to content
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

Merged
merged 26 commits into from
Jan 8, 2025
Merged

Add sentry #589

merged 26 commits into from
Jan 8, 2025

Conversation

toddkao
Copy link
Collaborator

@toddkao toddkao commented Dec 17, 2024

Add sentry integration
Add session replay, auto recording when error occurs
Add messages for wallet connected/wallet disconnected

Copy link

changeset-bot bot commented Dec 17, 2024

🦋 Changeset detected

Latest commit: 85585ef

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@skip-go/widget Patch
nextjs Patch

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

Copy link

vercel bot commented Dec 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
widget-nextjs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 7, 2025 5:26pm

@toddkao toddkao force-pushed the sentry-integration branch from 5f29aef to 37ab8fe Compare January 7, 2025 16:24
@@ -96,6 +97,7 @@ export const setSwapExecutionStateAtom = atom(null, (get, set) => {
}
},
onTransactionBroadcast: async (txInfo) => {
setUser({ id: txInfo?.txHash });
Copy link
Collaborator

@ericHgorski ericHgorski Jan 7, 2025

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?

Copy link
Collaborator Author

@toddkao toddkao Jan 7, 2025

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 });
Copy link
Collaborator Author

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

Copy link
Collaborator Author

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();
Copy link
Member

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

Copy link
Collaborator Author

@toddkao toddkao Jan 7, 2025

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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@toddkao toddkao merged commit b634b5a into staging Jan 8, 2025
5 checks passed
@toddkao toddkao deleted the sentry-integration branch January 8, 2025 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants