haskal/jiti-meet - GitLain - Git with a cup of Lain

Author	SHA1	Message	Date
James Carbine	5b10d8f5ef	Add config to hide logo-deep-linking on deeplinking page (#7346 ) This adds the ability to configure hiding the logo on the deep linking page. HIDE_DEEP_LINKING_LOGO defaults to false in the config. The implementation also defaults to showing the logo if HIDE_DEEP_LINKING_LOGO is missing from the config.	2020-08-10 09:30:16 -05:00
Bettenbuk Zoltan	0598e7369b	ref: eslint-config-jitsi@1.0.3	2020-05-20 17:14:29 +02:00
Saúl Ibarra Corretgé	dd23ed09ad	deps: react-native@0.60	2019-08-21 11:12:56 +02:00
Leonard Kim	d65a068fdb	feat(deep-linking): hide web button on unsupported browsers	2019-06-07 07:36:20 -07:00
Hristo Terezov	840c0190c4	fix(deep-linking): Don't rely on custom scheme	2019-05-24 12:51:14 -07:00
Bettenbuk Zoltan	2a5adfc601	Remove some Flow annotations	2019-03-25 13:53:08 +01:00
Saúl Ibarra Corretgé	c025c7e132	flow: tame the beast 🔥🔥🔥	2019-03-21 14:47:55 +01:00
Saúl Ibarra Corretgé	155e02bbfb	core: refactor routing Unfortunately, as the Jitsi Meet development evolved the routing mechanism became more complex and thre logic ended up spread across multiple parts of the codebase, which made it hard to follow and extend. This change aims to fix that by rewriting the routing logic and centralizing it in (pretty much) a single place, with no implicit inter-dependencies. In order to arrive there, however, some extra changes were needed, which were not caught early enough and are thus part of this change: - JitsiMeetJS initialization is now synchronous: there is nothing async about it, and the only async requirement (Temasys support) was lifted. See [0]. - WebRTC support can be detected early: building on top of the above, WebRTC support can now be detected immediately, so take advantage of this to simplify how we handle unsupported browsers. See [0]. The new router takes decissions based on the Redux state at the time of invocation. A route can be represented by either a component or a URl reference, with the latter taking precedence. On mobile, obviously, there is no concept of URL reference so routing is based solely on components. [0]: https://github.com/jitsi/lib-jitsi-meet/pull/779	2018-07-11 22:58:41 -05:00