Fix nested create, upsert and update on lists of inputs

[megawubs]

• Added or updated tests
• Added Docs for all relevant versions
• Updated CHANGELOG.md

Resolves #1315

Changes

Pass a new instance of the model to the actual update method.

Breaking changes
None

[spawnia]

@megawubs the branch was quite out of date. There is a GitHub bot which automatically keeps your forks up to date: https://probot.github.io/apps/pull/ (Beware that it nukes any changes you made on the master branch of any fork)

[spawnia]

Concerning 26a9406, we can not change that until we drop support for PHPUnit 6.

[megawubs]

@spawnia does this need an update on the docs?

[megawubs]

Concerning 26a9406, we can not change that until we drop support for PHPUnit 6.

Ah ok, i'll revert that then

Did you already revert it?

[spawnia]

@spawnia does this need an update on the docs?

We actually have an example in the docs that is now fixed:

input CreateTaskInput {
  name: String!
  notes: [CreateNoteInput!] @create
}

[megawubs]

@megawubs the branch was quite out of date. There is a GitHub bot which automatically keeps your forks up to date: https://probot.github.io/apps/pull/ (Beware that it nukes any changes you made on the master branch of any fork)

🤔 I did a merge with upstream before I started. Never mind, looks like it still contains the fix.

[spawnia]

I did a merge with upstream before I started. Never mind, looks like it still contains the fix.

AFAIK, doing that in PHPStorm does not automatically pull upstream?

[megawubs]

I think this is everything right?

[megawubs]

I did a merge with upstream before I started. Never mind, looks like it still contains the fix.

AFAIK, doing that in PHPStorm does not automatically pull upstream?

Did it through command line git.

[spawnia]

I think this is everything right?

Yeah, great job! Thanks a lot for taking the time to write proper tests. I am going to release a new version right now.

[lorado]

Did I miss something? I thought there is no need to use @create/@update on nested mutations.

input CreateUserInput {
    name: String
    tasks: [CreateTaskInput!] @create
}

It still works also without @create on tasks field, right? I don't understand the use case.

[spawnia]

@lorado without @create, you would have to add an intermediary input like this:

input CreateUserInput {
    name: String
    tasks: [CreateTaskHasMany!]
}

input CreateTaskHasMany {
    create: [CreateTaskInput!]
}

You can skip that layer if you know that all you are ever going to do with that relation is specifically create.