Nico Domino
Nico Domino
@webface If thats the schema you've used, then the `accessToken` field, for example, should have been available via `access_token` due to your `@map("access_token")` mapping. Give reapplying that schema a shot...
@williamluke4 anything to do here from our side?
Hey william, thanks for this! You probably saw it, but theres an issue/PR related to this in the core repo already as well: https://github.com/nextauthjs/next-auth/pull/2108 + https://github.com/nextauthjs/adapters/issues/130 Balazs initially said he...
`nextauthjs/next-auth` has been migrated to a monorepository. The adapters code can now be found there under `packages/adapter-*`. Thanks for your interest in the project!
Great, thanks! In general, looks good to me. We're currenlty on a break merging new features (like new providers). So I've labelled this PR as "ready" so the other maintainers...
Reopening
@Tian-que yes, as mentioned above. We are striving to have all our providers written in typescript. Are you still interested in getting this provider merged? Can you make the TS...
> > @Tian-que yes, as mentioned above. We are striving to have all our providers written in typescript. > > Are you still interested in getting this provider merged? Can...
Seeing the same error as @athammer. Is there still no way to disable the sentry server-side error capturing in `@sentry/nextjs`?
I ended up rewriting my one `runtime: experimental-edge` route to just be a normal node style API route for now to keep server-side error capturing everywhere else as well. Thanks...