Order of parsing with escapes returns errors depending on position in the query

[adkron]

Environment

Erlang/OTP 20 [erts-9.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Elixir 1.6.0 (compiled with OTP 20)
absinthe 1.4.12
absinthe_relay 1.4.3

Including a test on the master branch.

Expected behavior

There is an example test for the master branch at BinaryNoggin@4573a9f

I expect that the order of parsing with escape characters to parse no matter the position of the keys and values.

Actual behavior

 {:error,
             %Absinthe.Blueprint{
               adapter: nil,
               directives: [],
               errors: [],
               execution: %Absinthe.Blueprint.Execution{
                 acc: %{},
                 adapter: nil,
                 context: %{},
                 fields_cache: %{},
                 fragments: %{},
                 result: nil,
                 root_value: %{},
                 schema: nil,
                 validation_errors: [
                   %Absinthe.Phase.Error{
                     extra: %{},
                     locations: [%{column: 0, line: 1}],
                     message: "illegal: \") { name } }",
                     path: [],
                     phase: Absinthe.Phase.Parse
                   }
                 ]
               },
               flags: %{},
               fragments: [],
               input: "{ post(title: \"title\\\\\", body: \"body\") { name } }",
               name: nil,
               operations: [],
               result: %{},
               schema: nil,
               types: []
             }}

Relevant Schema/Middleware Code

BinaryNoggin@4573a9f

I created a test to show this happening.

[adkron]

There is no error if the input has a return after each item. It is a small workaround, but it might work for some people.