1
Improved Error Handling
Source: supabase/supabase#17538 · opened by @faizanraso
When creating a new bucket in the Storage section of a project, I kept trying to name the bucket "TestBucket", but I didn't notice the note that said capital values can't be used. When the error toast appeared, it only said invalid name. I think it may be helpful to show either an improved error message that lets you know what was wrong in the bucket name you selected, or live error handling when you're typing in the name (i.e. change the input border to red when you enter an invalid character").
Would love to create a PR for this if someone can direct me in how I should approach this problem.
Current Error Handling: <br>
<img width="1512" alt="Screenshot 2023-09-18 at 4 01 52 PM" src="
Would love to create a PR for this if someone can direct me in how I should approach this problem.
Current Error Handling: <br>
<img width="1512" alt="Screenshot 2023-09-18 at 4 01 52 PM" src="
No pledges yet. Be the first to back this.
Comments
Similar requests
Standardize Error Codes Across Supabase Ecosystem
1 vote · 0 comments
Make `error` codes non-optional for better error handling on the client side
4 votes · 0 comments
Send error codes for errors
3 votes · 0 comments
More specific reasons for the WeakPasswordReasons type
4 votes · 0 comments
Proper Error Propagation for Triggers on auth.users Table
2 votes · 0 comments
No comments yet.