Inconsistency in returned value for schema with transformation and default value

[mckacz]

Describe the bug

Hi, I've noticed the following unexpected behavior:
When using transform() with default() there is inconsistency in returned value between undefined and {} input.

To Reproduce

import * as yup from "yup";

const baseSchema = yup
  .number()
  .transform(v => v * 1000)
  .default(1);

console.log(yup.object({ value: baseSchema }).validateSync({})); // { value: 1 }
console.log(yup.object({ value: baseSchema }).validateSync(undefined)); // { value: 1000 }

Full test suite:
https://codesandbox.io/s/yup-transform-with-default-inconsistency-3tewl?file=/index.test.ts

Expected behavior

The same value for each case - either default value with or without transformation applied.

[jquense]

Ok so the reason for this is because in the undefined case, the object is being defaulted to {value: 1} initially because: https://github.com/jquense/yup#object-schema-defaults

In the other case, the input is not undefined, so the default object isn't used but value is still undefined. Since there is no value to process no transforms are run, and you just get the default