-
Notifications
You must be signed in to change notification settings - Fork 16
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
Standardize method names #302
Conversation
🦋 Changeset detectedLatest commit: 14047b2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@danieleds Adding you as a reviewer to double check the docs are still ok. |
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.
LGTM
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.
@framini I have left a few comments
* **room.ended**<br> | ||
* **room.started**,<br> | ||
* **room.updated**,<br> | ||
* **room.ended**<br> | ||
* Emitted when the room session is, respectively, started, updated, or ended. |
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.
@framini these eol spaces were needed for intellisense, which otherwise puts everything on the same line. For readme instead, we need the <br>
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.
all other eol spaces which are not preceded by a <br>
are fine to be removed
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.
That's Prettier in action 🤔
setMicrophoneVolume(params: { volume: number }): Rooms.SetInputVolumeMember | ||
|
||
/** | ||
* Sets the input level for the member. |
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.
can you add an example real quick? e.g.
Sets the input volume for the member (e.g., the microphone input level).
|
||
/** | ||
* Sets the speaker output level. | ||
* Sets the output level. |
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.
same as above, this could be
Sets the output volume for the member (e.g., the speaker output level).
}): Promise<void> | ||
|
||
/** | ||
* Sets the input level for a given member. |
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.
could you add the same change as above?
setSpeakerVolume(params: { memberId: string; volume: number }): Promise<void> | ||
|
||
/** | ||
* Sets the output level. |
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.
same as above
The code in this changeset includes
setInputVolume
andsetOutputVolume
as future replacements forsetMicrophoneVolume
andsetSpeakerVolume
respectively.