-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: add condition to terminate actors #36
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think you're not building the command in the EboActor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice catch! Ended up adding a test to be sure that we're using & running the right command
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, lgtm 🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just 2 brief comments, after addressing lgtm
return FinalizeRequest.buildFromEvent( | ||
event as EboEvent<"RequestFinalized">, | ||
this.registry, | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we move this entire method to an isolated CommandsFactory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a TODO
comment already, in the docs of this method, for doing that hehe
@@ -3,12 +3,14 @@ import { NormalizedAddress } from "@ebo-agent/shared"; | |||
import { Address } from "viem"; | |||
|
|||
export type RequestId = NormalizedAddress; | |||
export type RequestStatus = "active" | "finalized"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
export type RequestStatus = "active" | "finalized"; | |
export type RequestStatus = "Active" | "Finalized"; |
should we do it this way to have consistent naming convention for statuses?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable!
🤖 Linear
Closes GRT-154
Description
Request.status
property to indicate the internal state of aRequest
EboRegistry