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
Group subscriber v2 terminate #410
Conversation
Pull Request Test Coverage Report for Build 1446
💛 - Coveralls |
8fe8cf7
to
2d769c9
Compare
@@ -70,9 +70,13 @@ | |||
]). | |||
|
|||
%% Subscriber API | |||
-export([ start_link_group_subscriber_v2/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.
nit: it's unfortunate that there's a _v2 in the name as the /1 arity makes it unambiguous. Maybe make the _v2 function a compat alias for start_link_group_subscriber/1, then drop the _v2 one when the old API is dropped?
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.
Not sure if I follow you here: brod_group_subscriber_v2:start_link/1
is an existing API that was introduced together with brod_group_subsriber_v2
behavior, so renaming it won't be BWC. I didn't add a similar new API for the old brod_group_subscriber
module, because I consider it problematic, and I hope to get it removed in the next major release (and rename brod_group_subscriber_v2
module into brod_group_subscriber
).
86251a5
to
c30e5fa
Compare
This PR introduces an optional
brod_group_subscriber_v2
terminate
callback.