-
Notifications
You must be signed in to change notification settings - Fork 153
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
"Delete mutations" schema on version 6 #5444
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
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.
LGTM, shall we move "MovieDeleteResponse" to "DeleteResponse" and generate it once?
public get deleteInfo(): string { | ||
return `${upperFirst(this.entityName)}DeleteInfo`; | ||
} |
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.
public get deleteInfo(): string { | |
return `${upperFirst(this.entityName)}DeleteInfo`; | |
} |
@@ -312,6 +330,16 @@ export class TopLevelEntitySchemaTypes { | |||
}; | |||
}); | |||
} | |||
|
|||
public get deleteType(): ObjectTypeComposer { |
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 add a static "DeleteResponse" rather than "MovieDeleteResponse"
Description
This PR updates the schema in v6 with delete mutations.
Translation is not yet implemented, so this is a partial feature