-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FunctionalFlowStep #31
Comments
Good point. Actually, the generate() method is supposed to be used only by the flow class so it might be also _generate() And looking at it the return type is too general. Also, the flow class should be already taking care of passing the right inputs so I don't know why I added the filtered_inputs check. required_keys is used in the flow class: llmflows/llmflows/flows/flow.py Line 76 in 3c4ceb7
|
If the two are that tightly interlinked, then you should have a runtime check that you have a flowstep instance. |
Why not use **kwargs here?
llmflows/llmflows/flows/functional_flowstep.py
Line 42 in 3c4ceb7
Then you can name keyword args to the function (i.e.,
generate
), and the remaining will be the arguments forflowstep_fn
, so this will go awayllmflows/llmflows/flows/functional_flowstep.py
Lines 58 to 60 in 3c4ceb7
Rename
flowstep_fn
toinner_fn
orstep_fn
; it's part of aflowstep
class, so the context is already clear.llmflows/llmflows/flows/functional_flowstep.py
Line 39 in 3c4ceb7
^ is not used.
The text was updated successfully, but these errors were encountered: