Need method of determining whether conversation is connected or not about twilio-video.js HOT 4 CLOSED

Hi @treyrich, thanks for the report. We did recently refactor the internals to be more strictly follow state transitions. I think there are two things we could do here

1. Be more lenient in Conversation's disconnect method—i.e. is it really useful to throw if disconnect is called twice?
2. Expose the Conversation state, either an isConnected or some other state property.

from twilio-video.js.

Right. I think either would work. I mean honestly I was able to refactor my code to cover most cases pretty well. But it's just nice if in your teardown code you're able to just call conversation.disconnect() without having to worry about it potentially throwing an error if it was previously disconnected. It can certainly be handled by the developer, but it seems like since the library is already storing the state that it's redundant for the developer to do so also.

Personally I think that it will promote better, more well thought out, code to go with option 2 and expose the conversation state in some way, and continue the strict checking.

from twilio-video.js.

That is good feedback, @treyrich—thank you. I will share it with the team.

from twilio-video.js.

Hi @treyrich,

We've recently made a number of changes to the Video SDK: it's now called twilio-video.js instead of twilio-conversations.js; we've also simplified the object model (no more invites, Conversations are replaced by "Rooms", etc.).

The full API docs can be found here, but importantly we've

• Added a state property to the Room (which is either "connected" or "disconnected"), and
• Multiple disconnects no longer throw.

Hopefully this improves over the Conversations behavior.

Best,
Mark

from twilio-video.js.