feat(typegen): make 1-to-1 relationships detection optional #641
Conversation
This file contains hidden or 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
phamhieu
approved these changes
Nov 2, 2023
avallete
pushed a commit
that referenced
this pull request
May 13, 2025
…etection feat(typegen): make 1-to-1 relationships detection optional
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?
Can't tailor typegen to PostgREST v9 vs. v10 differences - v9 doesn't support one-to-one relationships
What is the new behavior?
Make one-to-one relationships optional. When we generate the types, e.g. from http://api.supabase.com/api/v1#/projects/getTypescriptTypes , we can check the project's PostgREST version first and detect one-to-one rels only if the project has PostgREST v10+