Add option to initialize nullables, instead of setting them to null about graphql-codegen-factories HOT 4 CLOSED

Hey! I'm happy to bring in any improvement 👍

I just had a look at the fork but it seems to implement a few different things so I am not sure to identify the changes you are interested in.

Would you like for all nullable fields to be treated as non-nullable from the schema? Should it also be reflected in the types or only in the factories' return value?

So given the following schema:

type Post {
  id: ID
  title: String
  excerpt: String
}

It should generate:

interface Post {
  id: string;
  title: string;
  excerpt: string;
}

function createPostMock(props: Partial<Post>): Post {
  return {
    id: "",
    title: "",
    excerpt: "",
    ...props,
  };
}

Or the fields should remain nullable in the type but filled with default values in the factory:

interface Post {
  id: string | null;
  title: string | null;
  excerpt: string | null;
}

function createPostMock(props: Partial<Post>): Post {
  return { 
    id: "",
    title: "",
    excerpt: "",
    ...props,
  };
}

from graphql-codegen-factories.

Hey! The first thing you discussed would be amazing - so basically add a flag to treat nullables as non-nullable if you request - allowing generation of non-nullable data. I know this is a problem with my schema but it would really help me for testing and I think would be a great QOL improvement!

from graphql-codegen-factories.

Thanks for the suggestion, I can definitely see how that would be useful. It should be straightforward to implement, I'll look into it 👍

from graphql-codegen-factories.

@elibosley I just released v1.2.0 with this feature. See the documentation for an example of how you can configure it: https://gabinaureche.com/graphql-codegen-factories/configuration/schema#configmaybevaluedefault The gist is to set the maybeValueDefault configuration option to "{defaultValue}".

Let me know if you have any feedback 🙏

from graphql-codegen-factories.