Invalid object produced for optional properties that have multiple nested required properties

[lo1tuma]

Description

Similar to #106 there is another case where fishery produces a value that is incompatible to the defined type constraint.

To Reproduce

interface Bar {
    firstRequiredProperty: string;
    secondRequiredProperty: number;
}

interface Foo {
    optionalProperty?: Bar
}

const fooFactory = Factory.define<Foo>(() => {
    return {}; // I like to have the minimal shape of the interface as the default
});


const value = fooFactory.build({optionalProperty: { firstRequiredProperty: 'foo' } }); // produces type `Foo`, but the actual value does not conform to `Foo` because `optionalProperty.secondRequiredProperty` is missing

Additional context

I think #113 might be related. I’m aware of associations, but as far as I can see associations could only solve the issue when I’m willing to provide a default value for optionalProperty, which I do not want.