You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, thanks a lot for this library, it's really good already.
Coming from JS land, I used a lib called join-monster which basically enables to map a graphql query (or a subset of it) to an SQL query, which I find extremely useful. The way this works is by enabling the parsed graphql query's AST to be "traversed" in the graphql query resolver to generate an sql query (by "assembling" pieces of sql text annotated in the schema).
I a not sure how to do this in haskell yet, but I don't think it could work with classic resolvers, because we need both the JSON-equivalent schema (that is the graphql schema) and its SQL counterpart.
I thought about creating functions mapping graphql types to beam (or any other sql-like lib) instances. But i'd still need to access the parsed query AST in the resolvers... If someone has any clue about this I'd be grateful ! (I'm reading the graphq-api Internals section but I'm new to haskell so, it's not so simple)
The text was updated successfully, but these errors were encountered:
I'm not 100% sure, but think the place to start is with the result of the
`validate` function. That gives you something that's a known good GraphQL
query, with all of the references and so forth expanded out.
On Wed, 23 May 2018 at 18:29 theobat ***@***.***> wrote:
Hey, thanks a lot for this library, it's really good already.
Coming from JS land, I used a lib called join-monster
<https://github.com/stems/join-monster> which basically enables to map a
graphql query (or a subset of it) to an SQL query, which I find extremely
useful. The way this works is by enabling the parsed graphql query's AST to
be "traversed" in the graphql query resolver to generate an sql query (by
"assembling" pieces of sql text annotated in the schema).
I a not sure how to do this in haskell yet, but I don't think it could
work with classic resolvers, because we need both the JSON-equivalent
schema (that is the graphql schema) and its SQL counterpart.
I thought about creating functions mapping graphql types to beam (or any
other sql-like lib) instances. But i'd still need to access the parsed
query AST in the resolvers... If someone has any clue about this I'd be
grateful ! (I'm reading the graphq-api Internals section but I'm new to
haskell so, it's not so simple)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#182>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAHq6nY0qbnZmO0JWFQrpX1jHQUmAssiks5t1ZxfgaJpZM4UK4FD>
.
Hey, thanks a lot for this library, it's really good already.
Coming from JS land, I used a lib called join-monster which basically enables to map a graphql query (or a subset of it) to an SQL query, which I find extremely useful. The way this works is by enabling the parsed graphql query's AST to be "traversed" in the graphql query resolver to generate an sql query (by "assembling" pieces of sql text annotated in the schema).
I a not sure how to do this in haskell yet, but I don't think it could work with classic resolvers, because we need both the JSON-equivalent schema (that is the graphql schema) and its SQL counterpart.
I thought about creating functions mapping graphql types to beam (or any other sql-like lib) instances. But i'd still need to access the parsed query AST in the resolvers... If someone has any clue about this I'd be grateful ! (I'm reading the graphq-api Internals section but I'm new to haskell so, it's not so simple)
The text was updated successfully, but these errors were encountered: