Jimmy Jia
Jimmy Jia
@rowillia Ping! Does this seem like an interesting avenue to pursue?
See https://github.com/davidyaha/graphql-redis-subscriptions/blob/v1.4.0/src/pubsub-async-iterator.ts, for example, which, while not exactly first-party, also doesn't quite do the right thing.
It's worth keeping in mind FWIW that the issue isn't generator functions per se. It's about adapting external event sources (something like an observable) to an async iterable. Right now...
From the other thread, this is much worse than previously understood given https://github.com/tc39/proposal-async-iteration/issues/126#issuecomment-403454433. At the current point, `iterator.return()` is just not going to work for tearing down and cleaning up...
I'd love to have this as well. While I understand that, per https://github.com/graphql/graphql-js/pull/746#issuecomment-301554231, schema directives just seem like a very natural way to attach this sort of metadata to fields....
Yup, makes total sense. I think it wasn't totally obvious to those of us coming from the side of using programmatically constructed schemas that people used directives for that purpose...
Does anyone own this proposal, incidentally? The options I've seen floating around have looked like: ```graphql exposed directive @foo(...) on ... decorator +foo(...) on ... ``` Or have a special...
@IvanGoncharov Interesting! So the behavior in graphql-js currently doesn't follow the spec? And I imagine the same applies for Ruby, too, since that's what GitHub are using. I'll amend, thanks.
Oh, never mind, I misunderstood what `CoerceVariableValues` was doing.