-
Notifications
You must be signed in to change notification settings - Fork 7
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: timeline service keeps events in memory #3618
Conversation
6b390a7
to
3d8331b
Compare
EventEntry entry = 3; | ||
} | ||
|
||
message EventEntry { |
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.
EventEntry was created just so we can reuse the sumtype within Event
and CreateEvent
.
The extra level of wrapping is ugly everywhere else though...
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 suppose I can just repeat the oneof
in both places and it'd make it a lot nicer to deal with events everywhere (the 99% case)
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.
(removed now)
Module: event.DestVerb.Module, | ||
Name: event.DestVerb.Name, | ||
Entry: &pbtimeline.EventEntry{ | ||
Entry: &pbtimeline.EventEntry_Call{ |
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.
What's up with the nesting?
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.
46a4d29
to
330ca7d
Compare
closes #3626
Very simple implementation to be begin with.
Allows: