-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove single relationships #5819
base: 7.x
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: f4f3f45 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
d6e4024
to
ed732e2
Compare
3444c9c
to
f4f3f45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lovely! Just left some comments
@@ -176,6 +176,7 @@ export function createRelationshipFields({ | |||
userDefinedFieldDirectivesForNode: Map<string, Map<string, DirectiveNode[]>>; | |||
features?: Neo4jFeaturesSettings; | |||
}): void { | |||
// HERE? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// HERE? |
const isList = Boolean(getListTypeNode(field)); | ||
|
||
if (isRelationship && !isList) { | ||
console.warn( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would change this to be a validation rule, so that an error is raised before reaching make-augmented-schema
type ${typePost} @node { | ||
id: String | ||
content: String | ||
creator: ${typeUser}! @relationship(type: "HAS_POST", direction: IN) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this test no longer necessary?
type ${typePost} @node { | ||
id: String | ||
content: String | ||
creator: ${typeUser}! @relationship(type: "HAS_POST", direction: IN) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above, is there is any reason to delete this test rather than change the creator
type
Description
Removes 1-1 relationships