jitsi-meet

Commit Graph

Author	SHA1	Message	Date
Saúl Ibarra Corretgé	fbcdb250f4	fix(ts) fix build on macOS Why this line fails is a mystery, but it's only reproducible on macOS.	3 years ago
Robert Pintilii	7364c7f27b	ref(TS) Remove unnecessary ts-ignores	3 years ago
Saúl Ibarra Corretgé	eee096e0c0	fix(ts,build) fix TS error in web build	3 years ago
Robert Pintilii	4ee77b1f65	ref(TS) Convert some base files to TS (#12226 )	3 years ago
Saúl Ibarra Corretgé	e578f6c30f	feat(logging) migrate logging to config.js	3 years ago
Jaya Allamsetty	30fc04ba61	fix(logging): Add more details to onerror and onunhandledrejection errors.	5 years ago
paweldomas	bc43f00d28	feat: pass network info to LJM	6 years ago
Bettenbuk Zoltan	0598e7369b	ref: eslint-config-jitsi@1.0.3	6 years ago
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	8 years ago
Saúl Ibarra Corretgé	87fa8de815	feat(sanity): axe IE and Temasys plugin support 🔥🔥🔥	8 years ago
hristoterezov	f14095ecfc	feat(deep_linking): add analytics In order to be able to add analytics to the deep-linking pages the lib-jitsi-meet initialization has been moved so it happens earlier. The introduced `initPromise` will eventually disappear, once conference is migrated into React and / or support for Temasys is dropped. At that stage, it can be turned into a sync function which all platforms share.	8 years ago
Lyubo Marinov	3c31a60b32	Fix TypeError: Cannot read property 'isGuest' of undefined	9 years ago
Lyubo Marinov	7836fd1990	Introduce features/base/logging The functionality around logging including logging_config.js i.e. loggingConfig and the other classes and/or functions that initialize loggers for Jits Meet truly deserves a feature of its own. Start getting in that direction on both Web and mobile by introducing features/base/logging and bringing loggingConfig to mobile.	9 years ago
Lyubo Marinov	92e765ea21	Introduce features/base/config The config object defined by lib-jitsi-meet is not used by lib-jitsi-meet only, jitsi-meet respects its values as well. Moreover, jitsi-meet defined classes and/or functions which manipulate that config object. Consequently, it makes sense to move the config object and the associated classes and functions in a dedicated feature.	9 years ago
Lyubo Marinov	bce1610794	Simplify, comply w/ coding style Rename setStateProperties and setStateProperty to assign and set, respectively. Inspired by Object.assign, _.assign, and _.set.	9 years ago
Saúl Ibarra Corretgé	a1da6bff1a	[RN] Fix loading config from non-default domains When a conference is to happen in a domain which is not the defaut, its config is loaded and set. As part of this process, lib-jitsi-meet is disposed. Because disposing is asynchronous, events happen in this sequence: - set new config - dispose lib (which effectively wipes the config) - init lib This results in the library to be initialized without the loaded config, which was lost. This commit fixes that by delaying setting the config and re-initializing the library until it was disposed.	9 years ago
Lyubo Marinov	0ed85b9d25	Replace features/unsupported-browser SET_UNSUPPORTED_BROWSER with features/base/lib-jitsi-meet SET_WEBRTC_READY The error raised by JitsiMeetJS.init() is already in the state of features/base/lib-jitsi-meet so it's not a good design to store the same error in the state of features/unsupported-browser.	9 years ago
Lyubo Marinov	0b9160fb75	LIB_DID_DISPOSE, LIB_DID_INIT, LIB_WILL_DISPOSE, LIB_WILL_INIT	9 years ago
Lyubo Marinov	d2b2f98941	Fix typo	9 years ago
Lyubomir Marinov	52b3eaacb5	[RN] Fix passing config.js to JitsiMeetJS.init	9 years ago
Lyubomir Marinov	4997ae79e3	Fix toolbar's mute buttons when starting muted The toolbar's mute buttons depict respective features/base/media states. However, (un)muting is practically carried out by features/base/tracks. When the mobile app enters a conference configured to invite the joining participant to mute themselves, the tracks would be muted but the toolbar's mute buttons would not reflect that.	9 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.	9 years ago

4 Commits (3cb0df579ca5b8615dfba1b8b901bca1c8ca9ac4)