Adrian Velcich

I have tried: ```js import { GraphQLObjectType, GraphQLNonNull, GraphQLInputType, GraphQLInputObjectType, GraphQLString, GraphQLInt } from 'graphql' // import { CvU} //... export const CvUserType = new GraphQLObjectType({ name: 'CvUserType', description: 'Use...

I notice in the `mutationType` in the example, that the first parameter for `resolve: (root, inputPerson)` is coming through as `undefined`, even though `inputPerson` is fine, and accessible. Is this...

it probably needs to look more like this: ` mutation { createPerson(input: { firstName: "test" }) } ` `input` expects to receive an object with match fields. That will work,...

@yarnball no problem :) It can be done, as you say, without using an `input` object, it's just considered better style to use one, especially in large projects, to help...

Hi, I'm also interested in this. How can I either add mutations after the fact, or during the SchemaBuilder? I have forked the project and already made some other small...

@koskimas Hi Sam, I really need to implement mutations in my model. I've had a look at the code, added duplicate functions for _resolveForModel(), _filterForArgs() as _mutationsForModel(), _filterForMutationArgs() etc, added...

FWIW to anyone here, I've made a PR that adds (very) basic Mutation support in PR #30

@nasushkov Sorry, I didn't see your comment until now. Yes, I agree with you in principle. However, I don't think that's the whole story. Some Mutations do affect the entire...

@nasushkov Thanks for the feedback. As I mentioned, my PR is for a **_really_** basic version of Mutation support, and I welcome additional input. At this point. `objection-graphql` currently has...

Hi Sam, I am still getting the same problem. I saw that the 1.0.6 release was indeed downloaded during precompile, so I'm sure I've got the fixes. Error:java.lang.NullPointerException at com.memtrip.sqlking.preprocessor.processor.model.Column.assembleIsIndex(Column.java:60)...