Standardize Error Codes Across Supabase Ecosystem

[srothgan]

Chore

Describe the chore

While implementing error handling with supabase-js, I discovered three inconsistency issues with error codes:

1. Missing Database Error Codes: Database operations lack defined error codes, making it difficult to implement consistent error handling across all Supabase services.
2. Inconsistent Naming Conventions: Auth error codes use snake_case (e.g., unexpected_failure), while Storage and Realtime use PascalCase (e.g., UnknownError). This inconsistency complicates error handling implementation.
3. Duplicate Error Codes: Both Storage and Realtime services use identical error codes (e.g., TenantNotFound) but with different error messages and meanings, making it impossible to uniquely identify errors by code alone.

Proposed Solution

I propose standardizing error codes across all Supabase services:

• Adopt a consistent naming convention (all snake_case)
• Add namespace prefixes to avoid duplicates (e.g., storage_tenant_not_found vs realtime_tenant_not_found)
• Implement missing database error codes following the chosen convention

Benefits

• Improved developer experience with consistent error handling
• Clear distinction between errors from different services
• Complete error code coverage across all Supabase functionality
• More maintainable codebase with standardized error patterns

Additional context

While not critical for functionality, these improvements would significantly enhance the developer experience and allow for more robust error handling patterns. I'm willing to contribute PRs to implement these changes if the proposal is accepted.

[Hallidayo]

Hi @srothgan, Thanks for opening this one. I'm going to move this over to discussions/enhancements as a feature request.