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
The ONEONE/ONEMANY bit should be auto set from kins (need to look at both sides)
The primary bit needs to follow the GQL default logic (move?), and have a means to be explicitly set by the user without defining the full bitmap
The InternalId should be auto set from Kind (should be done independently of auto-create of _id field, as the user may have reason to explicitly define part of the _id field - particularly if in the future we decouple the name from function)
AndrewSisley
changed the title
Add PatchSchemasyntax sugar for RelationType in foreign relations
Add PatchSchema syntax sugar for RelationType in foreign relations
Aug 11, 2023
## Relevant issue(s)
Resolves#2287#1772
## Description
Replaces `FieldDescription.RelationType` with an `IsPrimary` boolean.
One notable effect of this that may not be easily visible in the
code-diff is that the schema ID will not change depending on whether it
is the primary side of a one-one or on the one side of a one-many - now
the schema only cares about the shape of the data, not what is on the
other side of the relationship.
…work#2288)
## Relevant issue(s)
Resolvessourcenetwork#2287sourcenetwork#1772
## Description
Replaces `FieldDescription.RelationType` with an `IsPrimary` boolean.
One notable effect of this that may not be easily visible in the
code-diff is that the schema ID will not change depending on whether it
is the primary side of a one-one or on the one side of a one-many - now
the schema only cares about the shape of the data, not what is on the
other side of the relationship.
Part of #1002
See also semi-related: #2287
The text was updated successfully, but these errors were encountered: