-
Notifications
You must be signed in to change notification settings - Fork 309
api: Rename StreamMessage
to ChannelMessage
#848
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
api: Rename StreamMessage
to ChannelMessage
#848
Conversation
StreamMessage
to ChannelMessage
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.
Thanks @Khader-1. LGTM. Moving on to the integration review.
775beb1
to
ecaf03a
Compare
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.
Thanks @Khader-1! Comments below.
I haven't read through the whole second commit in detail; one comment is about how it can be made easier to review.
/// Construct an example stream message. | ||
/// Construct an example stream channel. |
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.
"channel message"
StreamMessage streamMessage({ | ||
ChannelMessage channelMessage({ |
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.
Because this function eg.streamMessage
has a huge number of references (333 of them, says my IDE), its rename should go in its own commit, separate from editing other things that refer to StreamMessage
or "stream messages".
That'd help make the changes easier to review — including self-review to catch things like "example stream channel" noted above.
Closing this PR as part of pushing back the priority of the remaining portion of this issue #631: details at #631 (comment). Thanks again! |
Fixes parts of #631