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
We’d love your feedback to ensure everything runs smoothly!
Important Notes:
This update might require regenerating your database types. You can do this via the Supabase CLI (≥v1.207.8) or the dashboard. For instructions, check out our guide here.
Potential Issues
This version introduces stricter alignment between runtime behavior and type inference. As a result, some types might appear "broken" but are actually being corrected.
The main changes to be aware of:
The result of an embedding now correctly infers a single object or an array based on the relationship.
The result of an object embedding now more accurately identifies whether the result can be null.
Before reporting a bug, please double-check that the inferred types are truly incorrect based on your query and database schema.
Bug Reporting:
If your project is hosted on Supabase, please open a support ticket here and check "Allow Supabase Support to access your project temporarily." This will enable us to investigate your database types directly.
Alternatively, you can open an issue on GitHub. Please include:
The generated Database type used to instantiate the client (e.g., createClient<Database>(process.env.SUPABASE_URL, process.env.SUPABASE_ANON_KEY)). If possible a minimal SQL declaration resulting in such Database type.
The query where type inference failed (e.g., .from('which-table').select('which-query')).
postgRESTrelated to PostgRESTjavascriptPull requests that update Javascript code
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
🚀 Announcement: We’ve just released
supabase-js
version2.46.2-rc.3
, which resolves several type errors in the PostgREST client.Notable issues resolved:
!inner
/is not null
supabase-js#943We’d love your feedback to ensure everything runs smoothly!
Important Notes:
This update might require regenerating your database types. You can do this via the Supabase CLI (≥v1.207.8) or the dashboard. For instructions, check out our guide here.
Potential Issues
This version introduces stricter alignment between runtime behavior and type inference. As a result, some types might appear "broken" but are actually being corrected.
The main changes to be aware of:
null
.Before reporting a bug, please double-check that the inferred types are truly incorrect based on your query and database schema.
Bug Reporting:
If your project is hosted on Supabase, please open a support ticket here and check "Allow Supabase Support to access your project temporarily." This will enable us to investigate your database types directly.
Alternatively, you can open an issue on GitHub. Please include:
Database
type used to instantiate the client (e.g.,createClient<Database>(process.env.SUPABASE_URL, process.env.SUPABASE_ANON_KEY)
). If possible a minimalSQL
declaration resulting in suchDatabase
type..from('which-table').select('which-query')
).npx tsc -v
).Beta Was this translation helpful? Give feedback.
All reactions