35 Commits (8225f5e363aac1b46695c9b081b4b5b34ff7a5ae)

Author	SHA1	Message	Date
Saúl Ibarra Corretgé	bdd8400057	fix(rn) remove no longer needed hack ... RN no longer logs pprops in release builds.	3 years ago
Saúl Ibarra Corretgé	c84e6eecdd	feat(rn) drop incoming call handling ... This "feature" has been dead (and most likely buggy) for years. The recommended way is for apps to implement their own incoming call handling and then call into the JitsiMeetActivity. We did not have those APIs back then.	3 years ago
Saúl Ibarra Corretgé	d121a63341	feat(rn) update React Native to version 0.66	3 years ago
Pavol Cvengros	2d27195652	chore(deps) update uuid package to 8.3.2 ... Co-authored-by: Saúl Ibarra Corretgé <saghul@jitsi.org>	3 years ago
Saúl Ibarra Corretgé	162a67fe8b	chore(lint) tame the (uppdated) linter	3 years ago
Calin Chitu	e0a2320d75	feat(native-participants-panel) renamed ParticipantsPanel to ParticipantsPane and created modal	3 years ago
Saúl Ibarra Corretgé	6e679f952f	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.	5 years ago
Bettenbuk Zoltan	0598e7369b	ref: eslint-config-jitsi@1.0.3	5 years ago
Saúl Ibarra Corretgé	caabdadf19	rn,polyfills: refactor all mobile polyfills ... Move all polyfills to a standalone feature, which gets imported before anything else in the mobile entrypoint. This guarantees that any further import sees the polyfilled environment.	5 years ago
Saúl Ibarra Corretgé	062bc13d4f	rn,storage: fix not using a persistent localStorage ... In 1ffd75c0a6 we switched to using the localStorage wrapper provided by js-utils, which checks for window.localStorage's availability very early. Our polyfill must be applied earlier that any such import. Here we are importing it in the entrypoint, which means no code ran before this, literally.	5 years ago
Saúl Ibarra Corretgé	902da8cc4f	rn: add native loggers ... These provide the ability to integrate the SDK with some other application loggers. At the time this was written we use Timber on Android and CocoaLumberjack on iOS. In addition to the integration capabilities, a LogBridge React Native module provides log transports for JavaScript code, thus centralizing all logs on the native loggers.	5 years ago
Saúl Ibarra Corretgé	fa3888991f	rn: avoid logging initial props in release builds ... They may contain sensitive information.	6 years ago
Saúl Ibarra Corretgé	3fa5aed950	rn: drop deep / universal links handling from JS ... It's now all handled in the SDK an we'll get the new URLs via props.	6 years ago
Leonard Kim	29809ab024	ref(app): set url prop to state in componentDidUpdate ... This is done to kill off the last deprecated lifecycle usage. There is special logic within index.native to get a default meeting url by asynchronously fetching it, if a url is not passed initially. The url is then put onto state and overridable on subsequent prop updates.	6 years ago
Bettenbuk Zoltan	80e8afa9c1	[RN] Remove react-native-prompt	6 years ago
Bettenbuk Zoltan	b41bf22be7	Replace console with logger	6 years ago
Lyubo Marinov	8ff3ae0ab2	[Android] Introduce IncomingCallView (continued)	6 years ago
Saúl Ibarra Corretgé	ea22d12581	[Android] Introduce IncomingCallView ... It's a separate view (on the native side) and app (on the JavaScript side) so applications can use it independently. Co-authored-by: Shuai Li <sli@atlassian.com> Co-authored-by: Pawel Domas <pawel.domas@jitsi.org>	6 years ago
Saúl Ibarra Corretgé	bd301403c4	[RN] Fix app startup from a CallKit intent ... Story time. Currently the app can be started in 4 ways: - just tapping on the icon - via a deep link - via a universal link - via the phone's recent calls list The last 3 options will make the app join the specified room upon launch. React Native's Linking module implements the necessary bits to handle deep or universal linking, but CallKit is out of its scope. In order to blend any type of app startup mode, a new LaunchOptions module (iOS only) exports a getInitialURL function, akin to the one in the Linking module, but taking CallKit instents into consideration. This function is then used to make app startup with a URL consistent across all different modes.	7 years ago
Lyubo Marinov	f35578c803	[RN] Polyfill __filename ASAP	7 years ago
paweldomas	b74bede0e7	feat(web/RN): update React to v16 and React Native to 0.49	7 years ago
Lyubo Marinov	2e2129fa44	Import PropTypes from prop-types ... Prepare for React 16.	7 years ago
Lyubo Marinov	6545a7a1bb	Remove duplication	7 years ago
Saúl Ibarra Corretgé	0983ef48b5	[RN] Fix root component's prop types	7 years ago
Saúl Ibarra Corretgé	d5e89a60b7	[RN] Fix passing url prop to Root and App components ... React (pun intended) to prop changes, that is, load the new specified URL. In addition, fix a hidden bug in loading the initial URL from the linking module: we prefer a prop to the URL the app was launched with, in case somehow both are specified. We (the Jitsi Meet app) are not going to run into this corner case, but let's be defensive just in case.	7 years ago
Lyubo Marinov	61fd4e4ce4	[RN] Fix passing url prop to Root and App components	7 years ago
Lyubo Marinov	9bd6bbfd95	Fix jsdocs. Simplify the source code	7 years ago
Saúl Ibarra Corretgé	cc9249ba1a	[RN] Fix passing url prop to Root and App components ... React (pun intended) to prop changes, that is, load the new specified URL. In addition, fix a hidden bug in loading the initial URL from the linking module: we prefer a prop to the URL the app was launched with, in case somehow both are specified. We (the Jitsi Meet app) are not going to run into this corner case, but let's be defensive just in case.	7 years ago
Lyubo Marinov	5f64ccb97d	[RN] Naming	8 years ago
Saúl Ibarra Corretgé	4687c1f465	[RN] Add ability to skip the welcome page ... Also expose this in the native SDKs.	8 years ago
Saúl Ibarra Corretgé	79d51bc379	feat(App): remove obsolete config prop ... It's obsolete now, since config is handled in Redux. Also add a "defaultUrl" prop so emdedding applications can select what the default base URL is.	8 years ago
Saúl Ibarra Corretgé	5304660e14	[RN] Polyfill Symbol	8 years ago
Lyubomir Marinov	49b3b49f3e	Remove duplication ... The files react/index.native.js and react/index.web.js ended up having very similar source code related to initializing the Redux store. Remove the duplication. Additionally, I always wanted the App React Component to be consumed without the need to provide a Redux store to it.	8 years ago
Lyubomir Marinov	0912dbf130	Remove duplication, simplify, comply with coding style	8 years ago
Lyubomir Marinov	d55e0f70d9	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 2f23d98424 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.	8 years ago