Changing the type on 'update' and 'delete'

[ani-sha]

type Mutation {
  updateNote(input: MutateNoteInput!, where: UpdateNoteFilter): Note!
}

update or delete might return null in cases where it doesn't match the condition, also it can change a couple of rows instead of one. Suggested definition:

type Mutation {
 updateNote(input: MutateNoteInput!, filter: UpdateNoteFilter): [Note]
}

The same goes for delete.

cc: @rareddy @wtrocki @machi1990

[rareddy]

Actually, on delete I propose completely removing the Input and only have the filter like

type Mutation {
 deleteNote(filter: NoteFilterInput): [Note]
}

there is no need for input as the filter can present with ID to delete a single row or a filter to delete multiple rows. Moreover I like the return that is been done in Hasura like here https://hasura.io/docs/1.0/graphql/core/mutations/delete.html