best way to handle "complex" args

[chrisdrackett]

I'm curious if people have thoughts on the best way to handle args in nexus. For example I have the following code:

schema.extendType({
  type: 'Mutation',
  definition: (t) => {
    t.field('updateUser', {
      type: 'User',
      args: {
        name: schema.stringArg({ required: false }),
        settingCalendarsToSync: schema.arg({
          type: 'String',
          list: true,
          required: false,
        }),
      },
      resolve: async (
        _parent,
        {
          name,
          settingCalendarsToSync,
        },
        { db, userId },
      ) => {
        return await db.user.update({
          where: { id: userId },
          data: {
            name,
            settingCalendarsToSync: { set: settingCalendarsToSync },
          },
        })
      },
    })
  },
})

but I get an error like:

Missing the required argument `set` for field `settingCalendarsToSync` on `User`.

what is the best way to set something like this up? do I just need to add logic to handle null and/or undefined?

[chrisdrackett]

curious if others are running into things like this. Even something simple like a mutation to update user settings gets messier than I would like:

schema.extendType({
  type: 'Mutation',
  definition: (t) => {
    t.field('updateUser', {
      type: 'User',
      args: {
        name: schema.stringArg({ required: false }),
        settingQuickActions: schema.arg({
          type: 'LogType',
        }),
        settingDefaultItem: schema.arg({
          type: 'ItemType',
        }),
        settingCalendarsToSync: schema.arg({
          type: 'String',
          list: true,
        }),
        settingLocationOnCreateItem: schema.booleanArg(),
        settingLocationInBackground: schema.booleanArg(),
      },
      resolve: async (
        _parent,
        {
          name,
          settingQuickActions,
          settingDefaultItem,
          settingCalendarsToSync,
          settingLocationOnCreateItem,
          settingLocationInBackground,
        },
        { db, userId },
      ) => {
        return await db.user.update({
          where: { id: userId },
          data: {
            name,
            ...(settingQuickActions ? { settingQuickActions } : {}),
            ...(settingDefaultItem ? { settingDefaultItem } : {}),
            ...(settingLocationOnCreateItem
              ? { settingLocationOnCreateItem }
              : {}),
            ...(settingLocationInBackground
              ? { settingLocationInBackground }
              : {}),
            ...(settingCalendarsToSync
              ? { settingCalendarsToSync: { set: settingCalendarsToSync } }
              : {}),
          },
        })
      },
    })
  },
})

the main thing I'm reacting to at this point is all the conditional spreads. I just don't see any other way to avoid wiping out these values when they are not passed in as part of the mutation.