jiti-meet/react/features/conference
Lyubo Marinov 8cd2bd272b Reduce direct read access to the features/base/participants redux state
As part of the work on fixing the problem with the multiplying
thumbnails, we've associated remote participant w/ JitsiConference.
However, there are periods of time when multiple JitsiConferences are in
the redux state (and that period is going to be shorted by
StateListenerRegistry). In order to give more control to the feature
base/participants, reduce the occurrences of direct access to the
features/base/participants redux state and utilize the feature's
existing read access functions. Which will allow us in the future to
enhance these functions to access participants which are relevant to the
current conference of interest to the user only.
2018-05-23 09:46:15 -05:00
..
components Reduce direct read access to the features/base/participants redux state 2018-05-23 09:46:15 -05:00
functions.js fix(lib-jitsi-meet): RTCBrowserType -> browser. 2018-01-22 15:56:06 -06:00
index.js [RN] Adjust Conference for the reduced UI mode (Coding style) 2018-02-13 13:24:10 -06:00
middleware.js feat(mobile): handle kicked out of the conference 2018-04-03 16:02:15 -05:00
route.js Updates config feature and whitelists options that can be overridden. (#2282) 2017-12-12 11:16:55 -08:00