Closed vladshcherbin closed 4 months ago
Thanks @vladshcherbin! This is a new feature from PostgREST v11 (using nested()
in v10 would result in an error), so flagging this as a feature request.
:tada: This issue has been resolved in version 1.12.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Bug report
Describe the bug
When using anti-join and not selecting any columns,
ParserError
is shown.Query:
Error:
The query is working and returns correct results, only typescript is showing this error with no types as a result. After adding any field (for example
car_images(id)
) the error disappears and typings are correct.Article with similar example (
nominations
relation): https://supabase.com/blog/postgrest-11-prerelease#anti-joinsExpected behavior
No typescript typings error, return type should not have this relation.
Screenshots
System information