Alec Helmturner

First off, I think we should definitely rope in the folks (@leonwilly @timcole @OutdatedVersion) that have done similar work over in #544, of which this actually appears to be a...

Just realizing that this post went in the wrong place, so quoting here (from #4347): > It's largely based off of the HTTP link and fetch adapter, but I'm using...

I'm noticing dropped events in my implementation, as well as bad error handling on server errors. If you spot / can think of any other shortcomings please let me know...

So I'm starting to get a pretty good feel for the internals, and updating my libraries for compatibility with 10.29 is going to help me grok some of the stuff...

Damn @iamnafets, I was literally going to go to bed after I finished that comment lol. I'll have to check out your PR tomorrow. But RE: subscriptions, I think it...

@iamnafets What are the pros/cons of defining the resolver as an async generator, as opposed to making it the return value of a normal resolver function? I'm genuinely asking... are...

@Sheraff I should have been more clear that I was trying to describe the DX when asking about my theoretical approach - the implementation details were just provided in case...

@iamnafets I have in mind some tricks on how to do it, but I'll see what issues I run into. Probably something like `ReturnType extends AsyncGenerator ? X : never`,...

Also, it occurs to me this API allows you to use object-oriented features, too. ```ts class StreamableObject { counter: number = 0; key: string | undefined; foo: string | undefined;...

@Sheraff I just finished up the edits on the class-based example above. What if the yielded result is always set as the `data` (on finish, `isResolved` becomes true and `data`...