-
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
Initial api design #10
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.
Is this just the bare API definition? The next step will be to set up the service loop? Specifically, we know the point of this is to run the hotshot_handle.get_event_stream() loop and push the events to all of the API subscribers.
Anyway, it looks like a good start. Get the clippy issues fixed, and we can merge, and continue from there.
Cargo.toml
Outdated
@@ -1,5 +1,5 @@ | |||
[package] | |||
name = "hs-builder-api" | |||
name = "hotshot-events-service" | |||
version = "0.1.1" |
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.
Let's start this at "0.1.0"
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.
Done
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.
Looks good.
Implements the bare minimum API specs to receive events from Hotshot.