Note: I’m using `graphcool-lib@next` and `event.co...
# prisma-whats-new
j
Note: I’m using
graphcool-lib@next
and
event.context.graphcool.pat
should now be
event.context.graphcool.token
but it isn’t set.
n
please use
graphcool-lib@0.0.3
should now be
event.context.graphcool.token
where does it say so?
j
I chose @next (so
0.0.4-beta4
) so I could port the email-password functions to TypeScript easily.
n
I'm currently updating all templates, here's an TS version of
email-password
using
0.3.0
j
Ah, cool.
(It says so here: https://github.com/graphcool/graphcool-lib/pull/9/files -
.pat
is being replaced with
.token
.)
I actually have TS implementations of all three functions ready, it’s just that
.token
isn’t set on the
Graphcool
instance that comes in with the event.
I’m happy to switch back to
0.0.3
though and use your versions if that’s what you recommend.
n
could you see if
.rootToken
works?
or just print out the
event.context
j
Sure, I’ll check
Yep,
.rootToken
is set.
n
oki, thanks! you can just set
.token
manually for now, we'll clean this up before releasing
0.0.4
🙂
j
As is
.pat
. It’s just that it’s missing from the TS types, so you can’t access it without TS failing to build.
n
ah right
j
Well, I guess graphcool-lib should use
.rootToken
perhaps instead of
.token
? I’m not sure what is desired here but as long as it tries to access
.token
(undefined),
graphcool.generateNodeToken
won’t work.
n
yes, that's definitely a change that needs to be made
we'll also check the
pat
for a while to stay backwards compatible
j
Sweet
Do you want me to file a bug report?
n
no, thanks! we'll release another
0.0.4
beta release later today
j
Nice, thank you!
n
j
Perfect, thank you very much! You guys are killing it with Graphcool 🙂