-
Notifications
You must be signed in to change notification settings - Fork 73
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
chore: update packages #295
Conversation
@@ -831,7 +831,8 @@ export class Intent { | |||
try { | |||
await this.ensureRegistered(); | |||
if (dontJoin) { | |||
deferredPromise.resolve(); | |||
// XXX: Should we return the passed in parameter if we didn't join, or empty? |
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.
I think returning the roomIdOrAlias
is ok as it imitates the success state after a join that's managed by this lib.
This is just for the public function join
, right? There doesn't seem to be another use of the return value.
public async join(roomIdOrAlias: string, viaServers?: string[]): Promise<string> { |
And we're changing this from void
to string
because that's what the public function join
promises, correct?
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.
Yup. Join should always return the room_id on success.
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.
Nice upgrade to TypeScript, as well as other dependencies.
No description provided.