Arda TANRIKULU
Arda TANRIKULU
It seems to be fixed with the latest Bun; https://github.com/oven-sh/bun/issues/12368#issuecomment-2493973621
Even if it is a bug in Bun, we fixed it with a workaround on our end in [email protected]
Closing in order to relax CI queue; It is already being worked on here; https://github.com/dotansimha/graphql-yoga/pull/3570
Adding the schema coordinate together with the existing `path` expose the schema information. Now the user knows that `hero`'s `heroFriends` is `[Human]`, and it has `name` in it. An attacker...
@EmrysMyrddin You're right but the security concern is still there, and if this schema coordinate property will be standard in the error object, then we should document this concern clearly.
You have to use `fieldConfig.subscribe` instead of `fieldConfig.resolve`, because as in the resolver map, `subscribe` is needed for subscription to initiate the event stream.
Closing this PR to reduce the noise in CI; We can't merge this until Node 18 reaches EOL.