Resolver of a nested Type is not triggered. #337

innovaweb-dev · 2021-05-26T23:09:21Z

AddressTC is a reusable Type, when UserTC or another Type is created or updated, I 973A whant to trigger validation automatically of AddressTC. If you know a better way to do that, I'll take it. With the code above, when I create or update User, resolever of AddressTC is not triggered.

// In this example I'll use UserTC but this can another type which also use AdressTC.

const UserTC = schemaComposer.createObjectTC({
    name: 'User',
    fields: {
        id: 'String',
        name: 'String',
        slug: 'String',
        actived: 'Boolean',
        registered: 'Boolean',
        address: AddressTC,
    }
});

const UserITC = UserTC.getInputTypeComposer()

UserTC.addResolver({
    kind: 'mutation',
    name: 'create',
    args: {
        data: UserITC
    },
    type: UserTC,
    resolve: async ({args: {data}, context}) => {
        // What I'll want it does : to trigger validation and geocode of AddressTC
        // What it does currently, GraphQL ignore AdressTC data and it just save data without validate
    },
})

// reusable Address Type

const AddressTC = schemaComposer.createObjectTC({
    name: 'Address',
    description: 'Type of address',
    fields: {
        street: 'String',
        number: 'String',
        postcode: 'String',
        city: 'String',
        comment: 'String',
        country: 'String',
        quality: QualityETC
    }
});

const AddressITC = AddressTC.getInputTypeComposer()

AddressTC.addResolver({
    kind: 'mutation',
    name: 'validation',
    args: {
        data: AddressITC
    },
    type: AddressTC,
    resolve: async ({args: {data}, context}) => {
        // When address is puted or updated :
        // => Make validation
        // => Geocode {Lat,Lng} with map provider 
        // Save in DB           
    },
})

Michael-vdL · 2021-07-13T19:58:33Z

Hello,

I believe you should look at the wrapped resolver methods in the docs.
Since you already have a validation resolver method, you should be able to do something along the lines of
const createUserWithValidation = UserTC.getResolver(‘create’).wrapResolver({ // call validation code here. })

Or, you can utilize middlewares (probably the correct approach). With middlewares, you can execute code before or after the resolver is executed. So you could write a middleware function that validates code prior to mutation.

`
function validateAddress () {
// validation code
}

const createUserWithValidation = UserTC.getResolver(‘create’).withMiddlewares([validateAddress]);
`

The bonus of the wrap method is you could make a fairly un-opinionated function that wrap all of your resolvers before they are built by schema composer and if the object contains a field of type AddressTC, it would enforce validation on all AddressTCs. With middlewares is probably cleaner.

Sorry for the lack of detail, I’m on iPad right now. If you need any additional information I can try to provide more detail later.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Resolver of a nested Type is not triggered. #337

Resolver of a nested Type is not triggered. #337

Resolver of a nested Type is not triggered. #337

Resolver of a nested Type is not triggered. #337

Comments