Skip to content

GraphQL: whether can support to class create mutation with a new subobject install of only a pointer #5971

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

Closed
jackeryjam opened this issue Aug 25, 2019 · 1 comment

Comments

@jackeryjam
Copy link

Sincerely thanking for bring such a wonderful function(parse + graphQL) to us. I love it deeply.And when I use it, I also meet some question as follows.

image

If I want to do this, first step I should create the a record of the pointer class and write the object id to it, where can I write the pointer class content in it to implement create the father class record and create the son class record at the same time only with a graphQL mutation.Like the following picture.
image

@davimacedo
Copy link
Member

@jackeryjam this issue was already tackled in this PR here and it will be available in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants