Is there any way to use `defaultNullableToNull` as `true` for all but one field?

[ankitprahladsoni]

Is your feature request related to a problem? Please describe.

We would like to keep the codegen small and eliminate any unnecessary data, so defaultNullableToNull set to true is one of the best options to use. However, we also have a nullable field, which we very frequently use to test our code/component for the majority of the use cases.

For example

type TestingData {
field1: String!
field2: String!
}

type User {
name: String!
testingData: TestingData
}

With defaultNullableToNull set to true, the aUser function always have testingData field set to null

Describe the solution you'd like

There should be a way to override defaultNullableToNull only for a few selected fields/types so that they are auto-filled by the mock data without us adding it manually all the time.

Describe alternatives you've considered

No response

Any additional important details?

No response

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ankitprahladsoni]

Bump

[ardeois]

Right now it's not possible, but you could create your own mock function that you reuse everywhere in your code

const aUserWithTestingData = (overrides?: Partial<User>) => {
   return aUser({ testingData: 'someDefaultValue', ...overrides });
} 

[ankitprahladsoni]

I'm currently following a similar pattern, but it isn't a very scalable solution, especially when there's a common option field, e.g., optionalTrackingID, which is an object and present in almost all the types. Since it is optional, the generated value is always null.
Not a big deal, but a little bit more flexibility would be appreciated.

[ardeois]

Ok I understand.
If you want to contribute, I suggest you first come with a plan of implementation and if that makes sense, you could open a pull request with the new option