You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Create a typed Supabase client with (types are generated with npx supabase gen types typescript --local
createClient<Database>(...)
Try to query data
2a. Using spread in select .select('...users (first_name, last_name)')
2b. Using newly introduced aggregate functions .select('from:from_time.min(), till:till_time.max()')
2a will type fail with PostgrestSingleResponse<ParserError<"Expected identifier at '...users (first_name, last_name'">>
2b will type fail with PostgrestSingleResponse<ParserError<"Unexpected input: .min(), till:till_time.max()">>
Expected behavior
No TypeScript errors
System information
OS: macOS
Version of supabase-js: ^2.39.7
Version of Node.js: 19.4.0
The text was updated successfully, but these errors were encountered:
@encima Would you know if there is a workaround? Right now, I'm casting all outputs to any before further processing. Maybe there is an casting-based approach utilizing the Supabase types that are already generated.
Bug report
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
npx supabase gen types typescript --local
2a. Using spread in
select
.select('...users (first_name, last_name)')
2b. Using newly introduced aggregate functions
.select('from:from_time.min(), till:till_time.max()')
2a will type fail with
PostgrestSingleResponse<ParserError<"Expected identifier at '...users (first_name, last_name'">>
2b will type fail with
PostgrestSingleResponse<ParserError<"Unexpected input: .min(), till:till_time.max()">>
Expected behavior
No TypeScript errors
System information
^2.39.7
19.4.0
The text was updated successfully, but these errors were encountered: