Replies: 2 comments 10 replies
-
I don't understand - these aren't user errors, they are errors in your usage of the API (sending invalid data to (edit - I've moved this to a discussion below (rather than Issue), GitHub's UI does not make this clear IMO since it uses the same color for "closed" vs "moved") |
Beta Was this translation helpful? Give feedback.
10 replies
-
Adding error handling to |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Support Question
I've encountered an issue where various CSV conversion errors are being logged to the console, which makes it challenging to capture and display meaningful messages to the user. These errors seem to abort the update process unexpectedly.
Attached is a screenshot illustrating the errors:
I am looking for a way to properly capture these errors so that I can provide a meaningful and user-friendly response instead of these raw messages. The current behavior is not conducive to a good user experience, as the console logs are not visible to the end-users.
Could you advise on best practices for capturing these errors within the code?
Ideally, I would like to intercept these errors before they hit the console, and then log them or display a custom error message to the user. Any pointers or examples would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions