haskal
/
jiti-meet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
jiti-meet/react/features/conference/index.js

5 lines
67 B
JavaScript
Raw Normal View History

[RN] Add display name label to tile view
2019-04-11 10:04:50 +00:00
// @flow
redux: refactor loading of middlewares and reducers Up until now we relied on implicit loading of middlewares and reducers, through having imports in each feature's index.js. This leads to many complex import cycles which result in (sometimes) hard to fix bugs in addition to (often) breaking mobile because a web-only feature gets imported on mobile too, thanks to the implicit loading. This PR changes that to make the process explicit. Both middlewares and reducers are imported in a single place, the app entrypoint. They have been divided into 3 categories: any, web and native, which represent each of the platforms respectively. Ideally no feature should have an index.js exporting actions, action types and components, but that's a larger ordeal, so this is just the first step in getting there. In order to both set example and avoid large cycles the app feature has been refactored to not have an idex.js itself.
2020-06-04 14:09:13 +00:00
Notify for kick and mute (#4328) * Updates kick showing who kicked us. * Notify participants that someone was kicked. * Shows notification to user who is remotely muted. * Updates the notification type. * Muted by notification for mobile. * Moves code to react and adds the kick notifications to mobile. * Updates lib-jitsi-meet.
2019-06-17 14:00:09 +00:00
export * from './actions';
Import jitsi/jitsi-meet-react#2f23d98 As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code.
2016-10-05 14:36:59 +00:00
export * from './components';