Replies: 1 comment 1 reply
-
This comes from graphql-code-generator, that we use internally. Anyway your
issue could be interesting.
We will investigate this possibility for sure.
Il Sab 28 Mag 2022, 18:51 Atlinx ***@***.***> ha scritto:
… Typetta currently does not import typescript files but instead parses
them. This prevents users from building graphql schemas through typescript
code.
So something like this doesn't work. Typetta doesn't pick up the injected
query type.
const someVar = `type Query { myCustomQuery(arg: String!): Boolean}`
export default gql`type User @entity @mongodb ] ...}${someVar}`
Having typetta pick up the custom generated schemas is useful because
typetta generate typescript types for the graphql it reads.
—
Reply to this email directly, view it on GitHub
<#222>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD7YBGIGCICE7KUB3YUTSTVMJMJTANCNFSM5XG55LHQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Typetta currently does not import typescript schema files but instead parses them. This prevents users from building graphql schemas through typescript code.
So something like this doesn't work. Typetta doesn't pick up the injected query type.
Having typetta pick up the custom generated schemas is useful because typetta generate typescript types for the graphql it reads.
Beta Was this translation helpful? Give feedback.
All reactions