Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Validate that a awaited promises rejection/exceptions are handled #346

Open
Samuel-Therrien-Beslogic opened this issue Jan 22, 2025 · 0 comments

Comments

@Samuel-Therrien-Beslogic
Copy link
Contributor

Follow-up to #331

#339 + #345 is ensuring that we have no more floating promises. And refactors catching promise rejections to always show something to the user.

However, there's still plenty of API calls done using await getApiClient(), and many of those likely just let the error bubble up / print to console, without showing any information to the user that something went wrong.

We should go through all await getApiClient() calls and validate that when they throw, something is shown to the user for the error produced.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant