I'm submitting a doc improvement request

• Regression
• Bug report
• Feature request
• Documentation issue or request (new chapter/page)
• Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

So the current doc is a bit misleading and causes confusion. I also learned that we might want to add some "heads up" notes about nullable fields as we have gone over it here: https://discord.com/channels/520622812742811698/1309067345943199774/1309067345943199774

Expected behavior

Instead of

nullable: for specifying whether a field is nullable (in SDL, each field is non-nullable by default);

IMO it is more concise to say: nullable: for specifying whether a field is nullable (in @nestjs/graphql, each field is non-nullable by default);

Minimal reproduction of the problem with instructions

n/a.

What is the motivation / use case for changing the behavior?

Less confusion after reading the doc

Environment

n/a.

For Tooling issues:

n/a.

Others:

One more thing that is also something I learned in that discord discussion and was not mentioned in the doc was how you should type your object types:

// wrong
@Field(() => String, {nullable: true}) 
id?: string;
// correct
@Field(() => String, {nullable: true}) 
id?: string | null;

And here is a relevant PR that lead to this issue: #3147