-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
Road to "V2" #2102
Comments
Another thing that would be nice to have, is to expand the decorator context. It would be nice to have those options. e.g. for improved observability |
Make it possible to publish to event-stream from a given actor context. suggestion:
|
First of all, I´m thinking that maybe we should just go semantic versioning and not make V2 something drastic.
We can gradually add breaking changes without redesigning large portions.
e.g. (take these with a whole hand of salt, just ideas)
Maybe
context.Send
should be async. so that you can await messages being pushed to a bounded mailboxMaybe
eventstream.Publish
should be async. so that you can await the event being consumed by all subscribers.Maybe
context.Parent
should be not nullable, and introduce a RootPid, Pid.None which could be used as the parent for top level actors.Thoughts and suggestions?
The text was updated successfully, but these errors were encountered: