Unicode U+0019 being rejected by Lexer #1448
Replies: 1 comment
-
Rightfully so, see https://spec.graphql.org/October2021/#SourceCharacter. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
Not too sure whether this is the right place to discuss this issue that has been bothering me for a while.
I always have a problem with sending a query that contains "invalid" unicode U+0019 , or \u0019 as the query is generated by a python service, e.g.
address: "Main\u00a0South\u00a0Rd,\u00a0O\u0019 Halloran
. Please correct me if I was wrong but I believe that this 'End of Medium' is considered as a valid unicode under UTF-8 standard. Shouldn't the GraphQL parser be accepcting it instead of throwing aSyntaxError
fromLexer.php
? Or is there a way to walk-around this check as we really would like to just skip this mutation/query validation step.Any helps or information will be much appreciated.
Framework: Symfony API Platform v2.7.0
graphqp PHP version: v14.11.6
PHP version: v8.0
Beta Was this translation helpful? Give feedback.
All reactions