You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2018. It is now read-only.
The ordering of the parameters in Connection#subscribe and in the service-side subscribe calls is incosistent. The names are confusing. The ordering as it appears in logging is confusing/inconsistent.
Make this better.
Everywhere a subscription is referenced, the names should indicate that events flow from left to right (sorry, RtL localities). That is, everywhere you see subscribe(a, b), it implies that events are published to a and fanned out to b.
The text was updated successfully, but these errors were encountered:
The ordering of the parameters in
Connection#subscribe
and in the service-sidesubscribe
calls is incosistent. The names are confusing. The ordering as it appears in logging is confusing/inconsistent.Make this better.
Everywhere a subscription is referenced, the names should indicate that events flow from left to right (sorry, RtL localities). That is, everywhere you see
subscribe(a, b)
, it implies that events are published toa
and fanned out tob
.The text was updated successfully, but these errors were encountered: