-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/Handle Reserved Names #207
Comments
Hello @nalchevanidze, Since a new issue has been opened, we move on here. I had read the related parts, the purpose of those functions were unclear to me at that time, due to the lack of a big picture. All I knew was: it parses & converts. The lesson learned here is we might need more comments in the original source code, and mention one can use I've tested your suggestions, it worked except for the generated documents. The output left the prime symbol just there. An example: # toGraphQLDocument rootResolver
input TestArgs {
type': String!
} ...I am afraid this isn't the intended behavior. The latest GraphQL spec:
... which allows the use of "type" as field name, so we might want get that fixed, too: # fixed
input TestArgs {
type: String!
} I don't know whether you're already working on the solution, but if you're busy, I'm willing to extend the |
my intention is that Haskell i will be glad if you extend the thank you :) |
Extend convertTo* to handle all Haskell 2010 reservedid
done, thanks @horus |
reserved name
type
is converted totype'
.there are
convertToJSONName
andconvertToHaskellName
functions responsible for it.TODO:
data
,default
, ....The text was updated successfully, but these errors were encountered: