Bug in parser: "extend type" declaration breaks parser

[nemanja-stanarevic]

Adding the following test to schema kitchen sink breaks the print test (visitor throws "Invalid AST Node")-

extend type Foo {
  seven(argument: [String]): Type
}

Root cause is a typo in the parser code - parser currently imports TYPE_EXTENTION_DEFINITION (instead of TYPE_EXTENSION_DEFINITION). This causes parseTypeExtensionDefinition to return a TypeExtensionDefinition value with kind field undefined, which in turn causes visitor to throw "Invalid AST Node".

I will submit a PR with the patch and updated test case shortly.

[leebyron]

Thanks for the investigation and fix!

[tjwebb]

Where is this extend documented? I see it mentioned only as an afterthought in the spec.

[leebyron]

It's experimental right now and thus has limited documentation. There's a proposal to add it to the spec.

[tjwebb]

How is it used? I'd like to be able to extend Query so that I don't need to define all of my root queries in one place.