-
Notifications
You must be signed in to change notification settings - Fork 12
Rename signaling channel to signaling #22
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
Conversation
| @type t :: %__MODULE__{pid: pid()} | ||
|
|
||
| @typedoc """ | ||
| Messages sent by the signaling channel to the peer. | ||
| """ | ||
| @type message :: {__MODULE__, pid(), message_content, metadata :: map} |
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.
Now I'm a bit concerned about these types, message in particular. Previously they were {SignalingChannel, , now they are {Signaling, }, so it may break people's code :/
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.
Do you think about Boombox, or about the community?
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.
Should we really care about it? The minor is bumped and I guess that the only things that use the messages in the form of {Signaling | SignalingChannel, pid, ...} are Boombox and WebRTC components that I am currently working on
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.
Right, I agree
No description provided.