supabase / supabase-flutter / 41427870403

94%

push

github

fix(postgrest): explain a maybeSingle() function call that returns no row object (#2116)

## What

Follow-up to #2113. `maybeSingle()` resolves to `PostgrestMap?`, so a
function call whose one row is not an object has no value it can resolve
to. Two examples are a function declared `RETURNS int[]`, which #2113
counts as one row as https://github.com/supabase/sdk/pull/307 requires,
and a function returning a scalar. Such a call used to fail with a bare
type cast error. It now throws a `StateError` that names the URL and the
type it received, and points to calling the function without
`maybeSingle()` or through `client.rpc.value`.

Supporting these results directly would mean changing the return type of
`maybeSingle()`. That return type is shared with
`from().select().maybeSingle()`, so the change would break every caller
reading the row as a map. The typed `client.rpc.value` already reads
such a value with its own type.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

<!-- coderabbit-ai-generated:v1 -->

## Summary by CodeRabbit

* **Bug Fixes**
* `maybeSingle()` now reports a clear error when a function call returns
a non-object value, including the returned type and URL. The error
suggests alternatives for reading the function result.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

4 of 4 new or added lines in 1 file covered. (100.0%)

12543 of 13325 relevant lines covered (94.13%)

6.64 hits per line