Omitting the blank fields to respect knex DB-level defaults

[singhArmani]

For keystone config as follows:

const { Keystone } = require('@keystone-alpha/keystone');
const { KnexAdapter } = require('@keystone-alpha/adapter-knex');
const { Text } = require('@keystone-alpha/fields');

const keystone = new Keystone({ name: 'Keystone To-Do List', 
  adapter: new KnexAdapter() 
 });

keystone.createList('Todo', {
  fields: {
    name: { type: Text },
    category: { type: Text, knexOptions: { defaultTo: 'misc' } },
  },
});

submitting a create list form inside Admin-UI, null was explicit in the mutation request for blank unedited fields. This was preventing the knex DB-level default to be applied correctly. But omitting the blank (unchanged) field, we managed to completely exclude it while making graphql mutation request and thus respecting the knew defaultTooption.

closes #1398

[changeset-bot]

🦋 Changeset is good to go

Latest commit: c42438e

We got this.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR