Nested Input Mutations for GraphQL-compliant nested mutations

[FMenet]

I have seen requests of Nested mutations (#89) for neo4j-graphql-js.
But the thing is, GraphQL specification seems to suggest it is not a good idea, as subfields should just be query fields to see what data changed.The preferable way could be to add a nested input type.

example :

mutation ManageWithInputs{
ManageLibrary(addCollection:
{ collName:'aName',
addBook:
   {bookName:'coolBook',
    addBookAuthor:"Me"}
})
{bookName
bookAuthor}

instead of :

mutation manageALibrary  {
ManageLibrary{
AddCollection(collName:'aName'){
   AddBook(bookName:'aCoolBook'){
       AddBookAuthor(authName:"Me"){
bookName
bookAuthor
   }
}
}

[michaeldgraham]

#608