feat(typegen): support --postgrest-v9-compat for --db-url
#1817
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kevcodez
approved these changes
Jan 5, 2024
sweatybridge
reviewed
Jan 5, 2024
soedirgo
force-pushed
the
feat/detect-o2o-flag
branch
from
b0be707 to
c0f26e7
Compare
|
Updated to use |
soedirgo
force-pushed
the
feat/detect-o2o-flag
branch
from
c0f26e7 to
b19551b
Compare
soedirgo
changed the title
--postgrest-v9-compat for --db-url
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
feature
What is the current behavior?
When running
supabase gen types typescriptwith--db-url, we can't check which PostgREST version the client lib will query against, and unfortunately PostgREST v10 has a breaking change which changes the format of a nested table for one-to-one relationships fromT[]toT | null. The generated types can only support one or the other.For the hosted platform and local dev this isn't an issue since we can detect the PostgREST version and switch between the 2 formats accordingly, but for
--db-urlwe need this to be configurable.What is the new behavior?
Add
--postgrest-v9-compatflag, which can only be used in conjunction with--db-url.