You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I thought on something similar to this when I did the Streaming brainstorm, but that would be a overkill at the time.
Basically, the connectors services could provide a method builder where they could use the streaming input to create the non-streaming content.
But the point of having a streaming in first place is that you can update your side the way you want while you still don't have the full object, for scenarios you want the full object, the other API is the place.
So, a valid example would be one where you actually Console.Write the output while building the object, and for that matter, only you know the details of your environment to update as the stream comes and we can't know that.
Looking forward to a scenario where this builder is justified where the non-streaming APIs don't already fit.
In this example, I've shown how it'd be nice to get the final result without having to create the final object myself.
Since this is what the alternative looks like...

The text was updated successfully, but these errors were encountered: