Unicode characters not supported in graphql descriptions
See original GitHub issueDescribe the bug Unicode characters such as emoji are not supported in graphql descriptions.
To Reproduce Excerpt from the github graphql schema:
"""
Emojis that can be attached to Issues, Pull Requests and Comments.
"""
enum ReactionContent {
"""
Represents the 😕 emoji.
"""
CONFUSED
. . .
}
The above emoji character is in the triple-quote comment, but the graphql antlr parser chokes on it. This blows up parsing of the schema, rendering it useless.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (8 by maintainers)
Top Results From Across the Web
April 2016 - GraphQL Specification
GraphQL documents are expressed as a sequence of Unicode characters. However, with few exceptions, most of GraphQL is expressed only in the original...
Read more >Special characters in GraphQL schema - Stack Overflow
The parser would throw an invalid schema because these characters have special meaning in graphql. GraphQL Spec. Punctuator:: one of !
Read more >Escaping special characters in JSON queries - Meedan Check
When performing a mutation on a media, I get an error when inserting special characters such as new lines \n or tabs \t...
Read more >Usage Notes for GraphQL Descriptors
The following special characters ? ~ ` # % ^ & * - @ + = \\ \" ; ' < > ,...
Read more >Identifiers Charset — Virtual DataPort Administration Guide
Unicode Mode¶ · The name is surrounded by double quotes and at least one character is uppercase. · Or, the name has characters...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
we decided to go behind the spec and allow all unicode chars … see #1603
@bbakerman I am inclined to change to allow full unicode characters, even if it is outside of the spec. What do you think?