-
-
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
Generate 'Schema.hs' Haskell GraphQL Type Definitions and Resolvers from 'Schema.gql' #184
Comments
It would be excellent to be able to do this with template-haskell in order to effectively create Haskell clients for 3rd party graphql sites. |
hi, @sordina i did not understand what do you mean, could you explain it with an example? |
Hi @nalchevanidze apologies for the rambling comment. I think I hadn't had much sleep when I wrote that! I'll explain my use-case:
Does that make sense? After working with some other GraphQL libraries from Haskell and other languages I've found that they are all a little frustrating to use, either too unsafe, or too underpowered, and it would be wonderful to see Haskell's strengths leveraged to give the best possible experience when working with GraphQL! |
as i see, you need Haskell Client with compile time query validation? like this. sounds good, i started working on it. #199 label of this issue was to generate GraphQL Api with morpheus CLI
generates whole api with dummy resolvers. so i am going to close it. your request is related to GraphQL Haskell Client. |
Hi @nalchevanidze awesome! Thanks! |
Actually, now that I reflect on this, the QQ example isn't quite what I'd envisioned, in that there isn't a datatype specialised to the fields requested, there doesn't seem to be a way to reference parameters, and the query isn't defined that returns that datatype. That said you're right this is a separate issue than the current one. |
Morpheus CLI
that convertsschema.gql
to haskell
API
with default Values:Api.hs
Deity.hs
so can be easily Migrated GraphQL api from
node.js
or any other LanguageThe text was updated successfully, but these errors were encountered: