jiti-meet/react/features/app/functions.web.js

// @flow

export * from './functions.any';

declare var interfaceConfig: Object;

/**
 * Returns application name.
 *
 * @returns {string} The application name.
 */
export function getName() {
    return interfaceConfig.APP_NAME;
}
[Android] Fix possible TypeError in multi-JitsiMeetView SDK consumers If multiple JitsiMeetView instances are created (not necessarily existing at once), it's possible to hit a TypeError when reading the React Component props of the currently mounted App. Anyway, in certain places we're already protecting against that out of abundance of caution so it makes no sense to not protect everywhere. 2018-05-10 04:45:24 +00:00			`// @flow`
Move interceptComponent.js out of features/base/util I don't like the file/function name, I'm not excited about the complexity of the logic it implements, and it's definitely a reusable piece worthy of being called a utility. 2017-04-14 16:48:40 +00:00
[Android] Fix possible TypeError in multi-JitsiMeetView SDK consumers If multiple JitsiMeetView instances are created (not necessarily existing at once), it's possible to hit a TypeError when reading the React Component props of the currently mounted App. Anyway, in certain places we're already protecting against that out of abundance of caution so it makes no sense to not protect everywhere. 2018-05-10 04:45:24 +00:00			`export * from './functions.any';`

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-06-29 07:58:31 +00:00			`declare var interfaceConfig: Object;`
Adds application name to the initJitsiConference options. 2017-10-13 20:34:27 +00:00
			`/**`
			`* Returns application name.`
			`*`
			`* @returns {string} The application name.`
			`*/`
			`export function getName() {`
			`return interfaceConfig.APP_NAME;`
			`}`