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
Is your feature request related to a problem? Please describe.
We should be able to tag actions. In particular, this could be used to do halt_after and halt_before.
Would have to do this at the class-level as well, should be straightforward. Also there's the possibility of name-clashes on halt. I'm OK with that due to the simplicity here.
Could also do this at the action level -- in the builder with_actions(some_action=action.with_tags(["requires_human_input"]). Would have to think about how to do this with function-based actions (TBD).
Describe alternatives you've considered
See above
Additional context
Something I've been mulling over for a while.
The text was updated successfully, but these errors were encountered:
On Wed, Dec 11, 2024 at 2:57 PM Elijah ben Izzy ***@***.***> wrote:
*Is your feature request related to a problem? Please describe.*
We should be able to tag actions. In particular, this could be used to do
halt_after and halt_before.
*Describe the solution you'd like*
@action(reads=[...], writes=[...], tags=["requires_human_input"])def act(state: State, human_input: ...) -> State:
...
app.run(halt_before=["requires_human_input"])
Would have to do this at the class-level as well, should be
straightforward. Also there's the possibility of name-clashes on halt. I'm
OK with that due to the simplicity here.
Could also do this at the action level -- in the builder
with_actions(some_action=action.with_tags(["requires_human_input"]).
Would have to think about how to do this with function-based actions (TBD).
*Describe alternatives you've considered*
See above
*Additional context*
Something I've been mulling over for a while.
—
Reply to this email directly, view it on GitHub
<#468>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARYMBZV773FDQ7KDL2FSUT2FC7MPAVCNFSM6AAAAABTOQXMN6VHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZTIMJZGYYTEOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Is your feature request related to a problem? Please describe.
We should be able to tag actions. In particular, this could be used to do halt_after and halt_before.
Describe the solution you'd like
Would have to do this at the class-level as well, should be straightforward. Also there's the possibility of name-clashes on halt. I'm OK with that due to the simplicity here.
Could also do this at the action level -- in the builder
with_actions(some_action=action.with_tags(["requires_human_input"])
. Would have to think about how to do this with function-based actions (TBD).Describe alternatives you've considered
See above
Additional context
Something I've been mulling over for a while.
The text was updated successfully, but these errors were encountered: