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

@thunderstore/dapper-ts: improve error handling #904

Closed

Conversation

anttimaki
Copy link
Contributor

Sentry handling doesn't need to be done on package level since we're
doing it on app level. Try to throw useful error messages, taking into
account I don't how much of the error stack is available on Sentry or
NextJs logs this way.

Refs no ticket

@anttimaki anttimaki requested a review from Oksamies November 10, 2023 13:57
Copy link
Contributor

@Oksamies Oksamies left a comment

Choose a reason for hiding this comment

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

Errors neatly lined,
In clarity, truth we find,
Good format, peace of mind.

Sentry handling doesn't need to be done on package level since we're
doing it on app level. Try to throw useful error messages, taking into
account I don't how much of the error stack is available on Sentry or
NextJs logs this way.

Refs no ticket
@anttimaki anttimaki changed the base branch from ts-api-error-handling to dapper-ts-package-listing November 21, 2023 09:54
@anttimaki anttimaki force-pushed the dapper-ts-error-handling branch from 44c8d08 to e30544f Compare November 21, 2023 10:05
@anttimaki
Copy link
Contributor Author

This PR can't be merged since a PR earlier in the stack doesn't pass CI due to changes for backend, that would be accounted for in a PR later in the stack. The changes will be merged as a part of #915.

@anttimaki anttimaki closed this Nov 22, 2023
@anttimaki anttimaki deleted the dapper-ts-error-handling branch January 19, 2024 08:02
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.

2 participants