GraphQL Allows Trailing Commas (By Design)

During a code review, we spotted a trailing comma in a GraphQL schema definition:

type SomeType {
  field1: String! # trailing comma
}

It looked like a mistake. But it worked fine.

The GraphQL spec explains:

Non-significant comma characters ensure that the absence or presence of a comma does not meaningfully alter the interpreted syntax of the document, as this can be a common user-error in other languages.

Commas are optional and insignificant everywhere in GraphQL — between arguments, fields, list items. The spec explicitly calls this out as a developer experience decision.

It's a small thing. But these small decisions compound. The sum of thoughtful DX details is the difference between a spec adopted by millions and one that quietly disappears.