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

14 lines
336 B
TypeScript
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 '../mobile/audio-mode/reducer';
import '../mobile/background/reducer';
import '../mobile/call-integration/reducer';
feat(mobile) adds ToggleScreenShare event and action.
2021-01-21 12:07:00 +00:00
import '../mobile/external-api/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 '../mobile/full-screen/reducer';
import '../mobile/watchos/reducer';
feat(share-room): disable Invite Others button when Share is visible (#12765) * feat(share-room): disable/enable Invite Others button
2023-01-12 10:13:18 +00:00
import '../share-room/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
fix(rn,navigation) wait until the root navigator is initialized There is a race condition in the root navigatior's initialization. It's possible that it's initialized a touch too late and SDK users who try to navigate to a conference end up stuck in the connecting screen because the navigator is null. This PR waits for it to be initilized by very unorthodox means, it's a horrible hack which we need to undo, but for that we need to break appart the inheritance relationship between App.{web,native}, AbstractApp and BaseApp because it's very inflexible. The flags are now initialized very early so the naviggator sees if the welcome page is enabled or not.
2022-05-06 09:20:22 +00:00
import './reducer.native';
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';