jiti-meet/react/features/base/conference
Saúl Ibarra Corretgé 774c5ecd18 rn: ensure the conference terminated event is always sent
Dear reader, I'm not proud at all of what you are about to read, but sometimes
life just gives you lemons, so enjoy some lemonade!

Joining a conference implies first creating the XMPP connection and then joining
the MUC. It's very possible the XMPP connection was made but there was no chance
for the conference to be created.

This patch fixes this case by artificially genrating a conference terminated
event in such case. In order to have all the necessary knowledge for this event
to be sent the connection now keeps track of the conference that runs it.

In addition, there is an even more obscure corner case: it's not impossible to
try to disconnect when there is not even a connection. This was fixed by
creating a fake disconnect event. Alas the location URL is lost at this point,
but it's better than nothing I guess.
2019-04-25 14:04:26 +02:00
..
actionTypes.js chore: use strings as action types 2019-03-21 14:47:55 +01:00
actions.js rn: ensure the conference terminated event is always sent 2019-04-25 14:04:26 +02:00
constants.js feat(1080p): pass new-style constraints to createLocalTracks (#2087) 2017-10-31 17:08:07 -07:00
functions.js [RN] Add conference navigation bar 2019-02-06 14:27:25 +01:00
index.js [RN] fix(Avatar): Match the implementation for web 2017-03-08 13:21:34 -06:00
middleware.js fix(base/conference): tracks not added to the conference 2019-03-27 10:06:59 +01:00
reducer.js feat(subject): UI 2019-03-12 23:03:58 +00:00