Argument need not be optional to have a default value defined

[gpj1]

Closes #

Description

Current documentation about Arguments says that "When an argument is optional, we can define a default value ..." This seems to be misleading because a default value for an argument can be defined irrespective of optional or mandatory argument.

[vercel[bot]]

@gpj1 is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel.

A member of the Team first needs to authorize it.

[linux-foundation-easycla[bot]]

• :white_check_mark:login: gpj1 / (9d514189d8744a846f6ce07afe15cb1b232e328d)

The committers listed above are authorized under a signed CLA.

[benjie]

Interesting nuance; technically you can’t define a default value for a non-optional argument, since an optional argument is one that is either nullable or has a default value, but this is a bit if a circular argument! Thanks for bringing this to our attention, definitely feels like the wording could be cleaned up 👍