Describe the bug
When making requests to the database via the OuterbaseConnection or the CloudflareD1Connection and an error is returned from either of those connections, the error never propagates back to the caller. If you look at the code null is actually hard coded as the return value there.
To Reproduce
- Fire a query that is doomed to fail
- Log out the error from
const { data, error } = db....
- Always see
null for error
Expected Result is to see an error object.
Expected behavior
Return an error in a standardized ConnectionError object similar to the type below:
export interface ConnectionError {
code: string
status: number
title: string
message: string
}
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
N/A