@GraphQLContext for @GraphQLMutation to modify input type

Hello!

I am trying to change the input type for a mutation, specifically for to-one relationships in our database.

So we have a business (has all the business specific info) that has a to-one relationship to the contact (has all the contact information) table.

I tried doing the following:

public Contact saveContact(
    @GraphQLContext
    Business business
) {
    // Create/update Contact information HERE
    return contactRepository.findById(business.getContactId()).block();
}

But do not see the input type modified at all.

Is this supported? What is the correct way to do this?

We are using SPQR version 0.10.1.

Thanks!

[kvakos]

In GraphQL you can have mutation structure equal to query structure. it brings unified graph for example

type Query {
  book(id: String): Book
}
type Book {
  name: String
  notes: [Note!]
}

and if you want to create mutation add note you can do it like

type Mutation {
  book(id: String) : BookOps
}
type BookOps {
  addNote(note : String) : NoteOps
}
type NoteOps {
  noteId: String
  note: String
  createdBy: String
}

Question is how to implement book.addNote mutation with spqr library. Any clue?

[kaqqao]

@meddox There’s no such thing as a nested mutation in GraphQL. You can read the spec for the details.

6.3.1 Normal and Serial Execution:

the resolution of fields other than top‐level mutation fields must always be side effect‐free and idempotent

I’ve also posted an explanation with references to the relevant spec articles in this Reddit thread. See my long comments, they go into the details and examples.

It comes down to asking if GET is the same as POST just without a body, why not write to the DB on a GET request?. You can. But it’s something that the tooling you use wasn’t made for.