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
I have had some typing issues with my queries, most of the errors are now resolved in postgrest-js 1.17 however it seems that the upgrade to 1.17 has been reverted on main, is there a reason for that ?
Is there something we could help with in order to upgrade postgres-js to 1.17 in this repo ?
To Reproduce
Writing a query where the join key is nullable and spreading the join is not making the inner columns nullable:
If the table2_id in table1 is number | null then both table_id and table_name should be null in the resulting type. This is not the case right now but is fixed in postgrest-1.17
Bug report
Describe the bug
I have had some typing issues with my queries, most of the errors are now resolved in postgrest-js 1.17 however it seems that the upgrade to 1.17 has been reverted on main, is there a reason for that ?
Is there something we could help with in order to upgrade postgres-js to 1.17 in this repo ?
To Reproduce
Writing a query where the join key is nullable and spreading the join is not making the inner columns nullable:
If the
table2_id
intable1
isnumber | null
then bothtable_id
andtable_name
should be null in the resulting type. This is not the case right now but is fixed in postgrest-1.17Expected behavior
The generated types should be correct
System information
Additional context
The text was updated successfully, but these errors were encountered: