Drop colon (:) for type definitions and $ from query variable about graphql-spec HOT 2 CLOSED

Thanks for this feedback. This is a lot, so let me try to address each point.

For colons in the type definition field arguments and variable definitions, we're hoping to do two things:

1. Create a visual mirroring between the definition of the field arguments and the usage of them.
2. More importantly, leverage existing knowledge of other languages where syntax works this way: Flow, TypeScript, Swift, amidst others.

is the dollar sign really required?

Yes, it syntactically avoids an ambiguity between a possible enum values and variables.

enum Color {
  red
  green
  blue
}

query coloredThing($color: Color) {
  variableThing: thing(color: $color)
  redThing: thing(color: red)
}

Also, variables have a different frequency and importance in a query language than they do in a programming language. When using a programming language, variables are often the most common token you use, so keeping them unadorned is important for legibility. In query languages, however, variables are fairly rare relative to data description identifiers. When variables are used, it's important to visually highlight them so that it's clear. We use the $ sigil as a way to visually identify variables.

from graphql-spec.

Makes sense, thanks.

from graphql-spec.