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

20 lines
599 B
JavaScript
Raw Normal View History

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
// @flow
import '../base/devices/reducer';
import '../e2ee/reducer';
ref(face-landmarks) refactor namings (#11307) * ref(face-landmarks) refactor namings * code review
2022-04-06 09:10:31 +00:00
import '../face-landmarks/reducer';
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
import '../feedback/reducer';
import '../no-audio-signal/reducer';
import '../noise-detection/reducer';
feat(participants-pane) implement participants pane
2021-04-21 13:48:05 +00:00
import '../participants-pane/reducer';
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
import '../power-monitor/reducer';
import '../prejoin/reducer';
fix(remote-control) skip on mobile Middlewares should not be loaded on mobile as there is no way to use the functionality.
2020-12-16 12:45:52 +00:00
import '../remote-control/reducer';
feat: Change the screenshare capture fps from UI. (#9438) * feat: Change the screenshare capture fps from UI. Add the ability to change the capture frame rate for screenshare from the UI. The fps becomes effective only on screen shares that are started after the setting is changed. * squash: add missing JSDOCs and translations for frames-per-second.
2021-06-28 07:48:16 +00:00
import '../screen-share/reducer';
feat(noise-suppression): Add noise suppression effect. (#11547) * add denoise effect * denoise prototype * improve rnnoise / add comments * revert some unnecessary changes * Add noise suppressor worklet * Send notification on failure * address code review * additional comments * additional comments * update package-lock * fix rebase changes * update rnnoise npm package * sort lang * adjust webpack performance hint * address code review * address code review * switch ns files to typescript * fix null-loader version, lang sort * fix lint * missing import * fix lint / address code review * use single action for ns state * move activation to thunk * increase node heap * copy noise-suppressor to deploy * fix ts lint
2022-07-20 12:31:17 +00:00
import '../noise-suppression/reducer';
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
import '../screenshot-capture/reducer';
import '../shared-video/reducer';
import '../talk-while-muted/reducer';
feat(virtual-backgrounds) add virtual background support
2021-02-18 15:52:47 +00:00
import '../virtual-background/reducer';
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
import './reducers.any';