feat: detect one-to-one relationships #491
Merged
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
This was referenced Oct 31, 2023
soedirgo
force-pushed
the
feat/detect-one-to-one-rels
branch
from
c04d8e4 to
a3cf5ca
Compare
soedirgo
force-pushed
the
chore/update-generated-types
branch
from
5a2a4d0 to
f0ec2e9
Compare
soedirgo
force-pushed
the
feat/detect-one-to-one-rels
branch
from
a3cf5ca to
32932bd
Compare
|
🎉 This PR is included in version 1.9.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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?
Doesn't detect one-to-one relationships - foreign table would be typed as
T[]What is the new behavior?
Foreign table on a one-to-one relationship would be typed as
T | null