Fields named "null" are incorrectly parsed as invalid

Version and Environment Details

Operation system:

Ubuntu 18.04.2 LTS

IDE name and version:

PhpStorm 2019.1 Build #PS-191.6183.95, built on March 28, 2019

Plugin version:

JS GraphQL (2.0.0)

Expected Behaviour

The following schema should be parsed without error:

input Foo {
  null: String
}

As per spec the only restriction on field names is the regexp /[_A-Za-z][_0-9A-Za-z]*/ and thus “null”, while probably not very common, is a valid field name.

Actual Behaviour

The following error is shown and it will break (in a non-obvious way) all other types depending on this one:

Invalid Syntax : Unexpected token: "null"

Steps to Reproduce / Link to Repo with Reproduction and Instructions

Copy/paste the schema above in probably any .graphql file.

I suspect the root of this issue actually is in another project. If you can confirm this, I’ll gladly open a new issue where it would be the most appropriate.

[jimkyndemeyer]

Fixed in the upcoming 2.4.0.

[jimkyndemeyer]

Thanks for the heads up.

There’s a number of breaking API changes when upgrading from graphql-java 12 to 14, some of which produce compile errors in the plugin. These also need to be addressed.

I can’t say when a fix will land, but I do see this as one of the next issues that need to be fixed.

Best regards, Jim.