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
The len_output method in the workflow implementation does not utilize handler-defined logic for calculating the length of the output, as seen in methods like json_output. Instead, it directly calculates the length of the current_output attribute, which causes inconsistencies when the handler is designed to redefine how the output length should be computed.
The text was updated successfully, but these errors were encountered:
Yeah I see what you mean. Although the len_output function in the workflowIter class was not acuatlly made to use the handler (I usually use the handler's method directly), I think that calling the handler in this case would provide a much better API.
The len_output method in the workflow implementation does not utilize handler-defined logic for calculating the length of the output, as seen in methods like json_output. Instead, it directly calculates the length of the current_output attribute, which causes inconsistencies when the handler is designed to redefine how the output length should be computed.
The text was updated successfully, but these errors were encountered: