Skip to content

Conversation

@rmosolgo
Copy link
Owner

@rmosolgo rmosolgo commented Nov 2, 2016

Oops, I just removed this in #366, But I think I shouldn't have. Here are some specs for this behavior in other parsers:

https://github.com/graphql/graphql-js/blob/master/src/language/__tests__/lexer-test.js#L166-L173
https://github.com/graphql/libgraphqlparser/blob/master/test/ParserTests.cpp#L134-L137

So I think the old way was right. But graphql-libgraphqlparser doesn't pass this test, and that's what made me second-guess it in the first place. So I'll look into that.

@rmosolgo rmosolgo merged commit dfdadb5 into master Nov 2, 2016
@rmosolgo rmosolgo deleted the fix-lexer-unicode branch November 2, 2016 02:28
@rmosolgo rmosolgo modified the milestone: 1.2.0 Nov 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants