Capture task outputs in a stream about griptape HOT 8 CLOSED

@collindutter, Indeed, using generators would be better. Wrote up this issue too quickly and had generator and iterable implementations mixed up in my head 😆.

from griptape.

@collindutter subtasks should be emitted for sure also.

from griptape.

Update on the issue: @collindutter is working on this after we dramatically simplified the initial design proposal. Should be added in the next version of Griptape.

from griptape.

@vasinov Wouldn't implementing __iter__ and __next__ methods require us to iterate over the structure class as opposed to the run method? Might it be better to use generators with yield?

from griptape.

@vasinov what do you think about emitting subtasks too? Necessary for any user interface that wants to show the entire flow.

from griptape.

@vasinov we can close this, right?

from griptape.

Yep, closing.

from griptape.

@vasinov apologies for bringing up an old thread, but I am not sure how to actually stream the text output? The examples and the event object only support token_count, ex: e.token_count whereas I want to stream the text itself, is there an example I can follow for that?

from griptape.