NestJS option unexpected disables initializeFieldsAsUndefined option

[shohoney]

I noticed that when NestJS is set to true, the field for initializeFieldsAsUndefined is forcefully set to false. Would it be okay for me to open a PR to allow options to override this behavior? Is there a specific reason that we're disabling this behavior for NestJS?

[stephenh]

Hi @shohoney ; I had to do a big of digging, but that option was added to solve this issue:

#492

Which is actually a Next.js issue with getServerSideProps.

I dunno, I don't remember if "NestJS users might be running in Next.js so enabled this for good measure" or "I just conflated NestJS and Next.js in my head" 🤔 :-D .

Either way, yep definitely fine with a PR that just removes that forced opt-in. Thanks!