Hey there .. I'm using this package <https://www.n...
# prisma-whats-new
k
Hey there .. I'm using this package https://www.npmjs.com/package/@playlyfe/gql in a VSCode plugin to allow for highlighting and autocomplete in graphql schema, but since
graphcool
only downloads custom-created types, the schema can't seem to find interfaces like
Node
and type
DateTime
. Is there a way around this? Does graphcool have some basic schema which can be provided to allow for this to work? Thanks.
n
hey @picosam you're running into the same issue as Lukas here 🙂
p
Thank you! Will try that now. Will this download my whole schema into this file, including all my types?
n
exactly
we should probably add this functionality to the CLI as well 🙂
p
I was just about to say that LOL
You’ll get there 😉
n
😂
p
OMG, I literally was just about to past that URL here now!
n
oh, I just created it
p
I went and looked at the open issues to see if it was already there ::)
n
hahaha
telepathy 🔭
👍 1
p
Yeah I saw #82 and #84 (mine) which are somehow related
n
good point
graphqls
is a weird extension though haha
p
Yeah I'll give you that!
n
ah, did you try using the
--output
option?
p
No!
n
or does it only accept
.graphcool
hmm
p
But does output work on push?
n
I think the
.graphcool
extension is currently required for many commands, so even if
--output
works, it won't work for other commands
p
Exactly
n
no but
graphcool push <file>
works
p
Even with a custom extension?
n
I did not try 😛
p
I think downloading the IDL schéma will resolve my issue for now anyways
n
in any case we should think about ways to support this
yea but now you have two files to manage...
p
True, but the IDL schema is read-only just for supporting the IDE plugin (and validation)
k
@nilan Now I'm getting duplicate type declaration errors, since there's
File
and
User
type in both
schema.graphql
and
project.graphql
.. how to proceed here? I can't modify the original schema.
@nilan I thought I could delete the types
File
and
User
, redownload the schema and then start adding new types in the separate schema, but then there wouldn't be the mutations and queries and such.
n
can you configure the package to only parse one file?
k
Yes, I can .. hmm, why didn't I think of that! Thanks, I'll try that 🙂